Triple
T15820292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xicomecoatl |
E383586
|
entity |
| Predicate | presentDayLocationOfDomain |
P31256
|
FINISHED |
| Object | state of Veracruz, Mexico |
—
|
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: state of Veracruz, Mexico | Statement: [Xicomecoatl, presentDayLocationOfDomain, state of Veracruz, Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayLocationOfDomain Context triple: [Xicomecoatl, presentDayLocationOfDomain, state of Veracruz, Mexico]
-
A.
presentDayLocationCorrespondsTo
chosen
Indicates that the current, real-world location of an entity matches or aligns with a specified reference location.
-
B.
presentDayCenter
Indicates that an entity currently serves as the central or primary focal point (e.g., administrative, cultural, or functional center) of another entity in the present day.
-
C.
presentDayNear
Indicates that one entity is located a short distance from another in the present time or current context.
-
D.
presentDayCityCountry
Indicates that a given city is located in a specified country in the present day.
-
E.
currentDisplayLocation
Indicates the location or context where something is presently being shown or rendered.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a6e6748190acb0791bd465587f |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.