Triple
T33160543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico City Metrobús Line 4 |
E848717
|
entity |
| Predicate | servesTransportHubType |
P70140
|
FINISHED |
| Object | airport |
—
|
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: airport | Statement: [Mexico City Metrobús Line 4, servesTransportHubType, airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTransportHubType Context triple: [Mexico City Metrobús Line 4, servesTransportHubType, airport]
-
A.
transportationHubType
Indicates the specific kind of transportation hub an entity is (e.g., airport, train station, bus terminal).
-
B.
isTransportHubType
chosen
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
-
C.
isGroundTransportHubFor
Indicates that a location functions as a central node or facility for organizing, coordinating, or serving ground-based transportation for another place or set of routes.
-
D.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
E.
servesTransportLinks
Indicates that one entity provides or supports transportation connections or routes for another entity or area.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 1, 2026, 1:28 a.m.