Triple
T9139885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrobús Line 3 stations |
E219295
|
entity |
| Predicate | serveCorridor |
P2566
|
FINISHED |
| Object | Line 3 bus rapid transit corridor in Mexico City |
—
|
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: Line 3 bus rapid transit corridor in Mexico City | Statement: [Metrobús Line 3 stations, serveCorridor, Line 3 bus rapid transit corridor in Mexico City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serveCorridor Context triple: [Metrobús Line 3 stations, serveCorridor, Line 3 bus rapid transit corridor in Mexico City]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
C.
hasServiceOnCorridor
chosen
Indicates that a service operates along, or is provided on, a specific corridor or route.
-
D.
corridorRole
Indicates a relationship where an entity functions as or is assigned the role of a corridor within a spatial or architectural context.
-
E.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f2537881908956a9b0516e2d49 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.