Triple
T25472226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro de Coatepec |
E638334
|
entity |
| Predicate | siteOfBattleOf |
P12233
|
FINISHED |
| Object | Huitzilopochtli vs Coyolxauhqui |
—
|
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 vs Coyolxauhqui | Statement: [Cerro de Coatepec, siteOfBattleOf, Huitzilopochtli vs Coyolxauhqui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteOfBattleOf Context triple: [Cerro de Coatepec, siteOfBattleOf, Huitzilopochtli vs Coyolxauhqui]
-
A.
battleTypeAtSite
Indicates the specific type or category of battle that occurred at a given site.
-
B.
battleBelligerentAtSite
Indicates that a particular belligerent (participant in a battle) was present and engaged in that battle at a specified site or location.
-
C.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
-
D.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
E.
battleSignificanceAtLocation
Indicates the degree of importance or impact that a particular battle has at a specified location.
- 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_69f5f752a4b08190bd3c98c98be204b7 |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:24 p.m.