Triple
T25472225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro de Coatepec |
E638334
|
entity |
| Predicate | placeOfBirthOf |
P1
|
FINISHED |
| Object | Huitzilopochtli |
—
|
NE NERFINISHED |
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: Huitzilopochtli | Statement: [Cerro de Coatepec, placeOfBirthOf, Huitzilopochtli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfBirthOf Context triple: [Cerro de Coatepec, placeOfBirthOf, Huitzilopochtli]
-
A.
placeOfBirth
chosen
Indicates the location where a person or other entity was born.
-
B.
creatorPlaceOfBirth
Indicates that the place specified is the location where the creator of an entity was born.
-
C.
birthPlaceAccordingTo
Indicates that an entity’s place of birth is given as a specific location according to a particular source or authority.
-
D.
cityOfBirthOfNamesake
Indicates that one entity is the city where the namesake (the person or entity after whom something is named) of another entity was born.
-
E.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2:24 p.m.