Triple
T34925519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tao Poon station |
E1007272
|
entity |
| Predicate | openedAsBlueLineInterchange |
P193798
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Tao Poon station, openedAsBlueLineInterchange, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsBlueLineInterchange Context triple: [Tao Poon station, openedAsBlueLineInterchange, 2017]
-
A.
openedOnBlueLine
Indicates that an entity was opened, initiated, or began operation specifically on the blue line (e.g., a blue-designated route, track, or service line).
-
B.
openedAsRedLineStation
Indicates that a station began operation specifically as part of the Red Line when it first opened.
-
C.
openedAsMetrolinkLine
Indicates that a railway line or route was inaugurated or began operation specifically as part of the Metrolink network.
-
D.
openedAsPurpleLineTerminus
Indicates that a station or stop was inaugurated serving as a terminus for the Purple Line.
-
E.
openedAsCurrentOrangeLineTerminus
Indicates that a location began operation specifically as the then-current terminus (end station) of the Orange Line.
- F. None of above. chosen
Provenance (4 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4 p.m.