Triple
T4909321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 9 (Mexico City Metro) |
E110193
|
entity |
| Predicate | openingDateSegment |
P12553
|
FINISHED |
| Object | 1987-08-26 Tacubaya–Centro Médico |
—
|
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: 1987-08-26 Tacubaya–Centro Médico | Statement: [Line 9 (Mexico City Metro), openingDateSegment, 1987-08-26 Tacubaya–Centro Médico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateSegment Context triple: [Line 9 (Mexico City Metro), openingDateSegment, 1987-08-26 Tacubaya–Centro Médico]
-
A.
openingDateLine16
Indicates the date on which line 16 was officially opened or began operation.
-
B.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
C.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
D.
openingDateOfFirstSpan
Indicates the date on which the first span (e.g., of a structure or project) was initially opened or put into service.
-
E.
expansionOpeningDate
chosen
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e99414081908c3d3283f563bba4 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.