Triple
T2367151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Lázaro |
E46007
|
entity |
| Predicate | isMajorTransitHubOf |
P2413
|
FINISHED |
| Object | eastern 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: eastern Mexico City | Statement: [San Lázaro, isMajorTransitHubOf, eastern Mexico City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTransitHubOf Context triple: [San Lázaro, isMajorTransitHubOf, eastern Mexico City]
-
A.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
B.
hasMajorRailwayStation
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
C.
isSuburbanStationOf
Indicates that a station is located in a suburban area and functionally serves as a subsidiary or outlying station of a main or central station.
-
D.
interchangeStation
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
-
E.
hasTransportHub
chosen
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc74b6bdc8190a12b2bcaa2dd7616 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.