Triple
T2710691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuicuilco |
E59851
|
entity |
| Predicate | approximateDestructionDate |
P33141
|
FINISHED |
| Object | around 1st–2nd century 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: around 1st–2nd century CE | Statement: [Cuicuilco, approximateDestructionDate, around 1st–2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDestructionDate Context triple: [Cuicuilco, approximateDestructionDate, around 1st–2nd century CE]
-
A.
demolitionYearApprox
chosen
Indicates that an entity was demolished in or around a particular year, where the year is an approximate rather than an exact value.
-
B.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
C.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
D.
traditionallyDestroyedAt
Indicates that something is customarily or historically destroyed at a particular time, place, or event according to tradition.
-
E.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7771a4819081904bd6b818b81b |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.