Triple
T12147169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zona Arqueológica de Cuicuilco |
E289354
|
entity |
| Predicate | estimatedOccupationStart |
P3418
|
FINISHED |
| Object | around 800 BCE |
—
|
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 800 BCE | Statement: [Zona Arqueológica de Cuicuilco, estimatedOccupationStart, around 800 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedOccupationStart Context triple: [Zona Arqueológica de Cuicuilco, estimatedOccupationStart, around 800 BCE]
-
A.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
-
B.
occupiedFrom
chosen
Indicates that an entity is in use or inhabited starting from a specified point in time.
-
C.
occupancyRequirement
Indicates that a condition specifies how many or which entities must be present in or using a particular space or resource.
-
D.
hostOccupation
Indicates that one entity serves as the primary job, profession, or role held by another entity.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.