Triple
T9346104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longyang Road station |
E224893
|
entity |
| Predicate | maglevServiceStartDate |
P87636
|
FINISHED |
| Object | 2004-01-01 |
—
|
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: 2004-01-01 | Statement: [Longyang Road station, maglevServiceStartDate, 2004-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maglevServiceStartDate Context triple: [Longyang Road station, maglevServiceStartDate, 2004-01-01]
-
A.
monorailOpeningDate
Indicates the calendar date on which a monorail system or line was first opened for public operation.
-
B.
inauguratedHighSpeedServiceIn
Indicates that an entity began or officially launched high-speed service (such as transportation or communication) in a specified location or region.
-
C.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
D.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
-
E.
openedAsMetraService
Indicates that a transportation facility or line began operating specifically as part of the Metra commuter rail service.
- 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f0e2ccc8190a68f1c96c0886660 |
completed | April 1, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:41 p.m.