Triple
T4177065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston METRORail |
E86502
|
entity |
| Predicate | greenLineOpeningDate |
P10389
|
FINISHED |
| Object | May 23, 2015 |
—
|
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: May 23, 2015 | Statement: [Houston METRORail, greenLineOpeningDate, May 23, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greenLineOpeningDate Context triple: [Houston METRORail, greenLineOpeningDate, May 23, 2015]
-
A.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
-
B.
line5OpeningDate
Indicates the date on which line 5 was first opened or began operation.
-
C.
monorailOpeningDate
Indicates the calendar date on which a monorail system or line was first opened for public operation.
-
D.
metroLineInaugurated
chosen
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
E.
railwayLineOpened
Indicates that a railway line began official operation or service on a specified date.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.