Triple
T9139689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Línea 2 del Metrobús de la Ciudad de México |
E219291
|
entity |
| Predicate | usesCorridor |
P5520
|
FINISHED |
| Object | Eje 2 Sur |
E781567
|
NE 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: Eje 2 Sur | Statement: [Línea 2 del Metrobús de la Ciudad de México, usesCorridor, Eje 2 Sur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eje 2 Sur Context triple: [Línea 2 del Metrobús de la Ciudad de México, usesCorridor, Eje 2 Sur]
-
A.
Eje 2 Sur
chosen
Eje 2 Sur is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
B.
Eje 3 Sur
Eje 3 Sur is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
C.
Eje 1 Sur
Eje 1 Sur is a major east–west arterial road in Mexico City that forms part of the city’s structured “eje vial” traffic network.
-
D.
Eje 5 Sur
Eje 5 Sur is a major east–west arterial road in Mexico City that runs through several neighborhoods, including Colonia del Valle.
-
E.
Eje 4 Sur
Eje 4 Sur is a major east–west arterial corridor in Mexico City that serves as an important route for public transportation and urban mobility.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f129c08190b6f053984cb7363f |
completed | April 1, 2026, 5:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09b75186c8190849f86b7e26093f1 |
completed | April 4, 2026, 5:02 a.m. |
Created at: March 30, 2026, 7:19 p.m.