Triple
T35908747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muni Metro |
E1038545
|
entity |
| Predicate | openedAsModernLightRail |
P194631
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Muni Metro, openedAsModernLightRail, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsModernLightRail Context triple: [Muni Metro, openedAsModernLightRail, 1980s]
-
A.
openedForLinkLightRail
Indicates that a facility, route, or segment has been opened specifically to serve or accommodate Link light rail operations.
-
B.
openedAsTramway
Indicates that a transportation line or route was originally inaugurated and operated as a tramway system.
-
C.
openedAsMetrolinkLine
Indicates that a railway line or route was inaugurated or began operation specifically as part of the Metrolink network.
-
D.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
E.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:07 p.m.