Triple
T2154839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uxmal |
E47862
|
entity |
| Predicate | mainPeriodOfFlourishing |
P15561
|
FINISHED |
| Object | Late Classic period |
—
|
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: Late Classic period | Statement: [Uxmal, mainPeriodOfFlourishing, Late Classic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPeriodOfFlourishing Context triple: [Uxmal, mainPeriodOfFlourishing, Late Classic period]
-
A.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
B.
flourishedAmong
Indicates that an entity thrived, prospered, or reached a peak of development within a particular group, environment, or context.
-
C.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
D.
flourishedAfter
Indicates that one entity reached its peak or period of prosperity subsequent to the flourishing or peak period of another entity.
-
E.
flourishedToCentury
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe64fdf081909a5ea6818bddd18c |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.