Triple
T1421040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teotihuacan civilization |
E30224
|
entity |
| Predicate | populationPeakEstimate |
P6809
|
FINISHED |
| Object | over 100000 inhabitants |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: over 100000 inhabitants | Statement: [Teotihuacan civilization, populationPeakEstimate, over 100000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationPeakEstimate Context triple: [Teotihuacan civilization, populationPeakEstimate, over 100000 inhabitants]
-
A.
populationAtPeak
chosen
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
B.
populationDensity
Indicates the number of individuals or entities occupying a unit area within a given region.
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
populationDemonym
Indicates the term used to refer to the people or inhabitants associated with a particular place or region.
-
E.
populationConcentration
Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c42210948190a8fb5e3f9ee3213b |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 8 p.m.