Guide
How Fogu resolves entities for extraction-ready technical content
Last modified:
Fogu maps stable IDs to answer chunks and citations.
Source: https://fogu.appStatistical Anchors
- 92% of answer blocks resolve to a canonical entity ID. (prod extraction logs) https://fogu.app/docs/entity-resolution-metrics
- 38ms median graph lookup after schema normalization. (runtime benchmark) https://fogu.app/docs/runtime-benchmarks
Extraction Chunks
definition
Entity resolution binds every mention to a stable canonical @id.
procedure
Publish answer capsules first, then map each claim to citation anchors.
caution
Changing entity IDs breaks historical retrieval and citation consistency.
FAQ
- How does Fogu keep entities disambiguated?
- Each entity uses a canonical @id and pages repeat that identifier in schema, chunks, and citation anchors.
- Why do answer capsules come first?
- Early concise answers improve extraction quality while later sections provide procedure and evidence depth.
Linked Entities
- Fogu (https://fogu.app/#fogu)
- Fogu Editorial Team (https://fogu.app/#editorial-team)
- Fogu Tech Documentation (https://fogu.app/#tech-docs)
- Fogu Organization (https://fogu.app/#organization)