Triple
T1450496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikal |
E31278
|
entity |
| Predicate | majorFlourishingPeriod |
P15561
|
FINISHED |
| Object | c. 600 to 800 CE |
—
|
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: c. 600 to 800 CE | Statement: [Tikal, majorFlourishingPeriod, c. 600 to 800 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorFlourishingPeriod Context triple: [Tikal, majorFlourishingPeriod, c. 600 to 800 CE]
-
A.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
B.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
C.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
D.
historicalPeriodOfMajorActivity
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
E.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55d923c8190957756f834f94462 |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.