Triple
T6303853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toluca |
E141323
|
entity |
| Predicate | distanceToMexicoCity |
P45441
|
FINISHED |
| Object | about 63 kilometres |
—
|
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: about 63 kilometres | Statement: [Toluca, distanceToMexicoCity, about 63 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMexicoCity Context triple: [Toluca, distanceToMexicoCity, about 63 kilometres]
-
A.
distanceFromMexicoCity
chosen
Indicates the measured distance between an entity’s location and Mexico City.
-
B.
distanceFromOaxacaCity
Indicates the spatial distance between a given place and Oaxaca City.
-
C.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
-
D.
distanceToMexicoBorder
Indicates the measured or estimated distance between a given location or entity and the border of Mexico.
-
E.
distanceToPhoenix
Indicates the measured or estimated distance between a given entity’s location and the city of Phoenix.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645e150881908b49a07914dcbfd8 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.