Triple
T7107161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya civilization |
E165616
|
entity |
| Predicate | peakPopulationCentury |
P6809
|
FINISHED |
| Object | 8th century |
—
|
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: 8th century | Statement: [Maya civilization, peakPopulationCentury, 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPopulationCentury Context triple: [Maya civilization, peakPopulationCentury, 8th century]
-
A.
populationStatus19thCentury
Indicates the population condition or demographic status of an entity during the 19th century.
-
B.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
C.
historicalPopulationCharacteristic
Indicates a relationship where an entity is associated with a demographic or population-related attribute that held true during a specific historical period.
-
D.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
E.
populationAtPeak
chosen
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.