Triple
T9772577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Underground station |
E237161
|
entity |
| Predicate | openedForDistrictLine |
P41908
|
FINISHED |
| Object | 1877 |
—
|
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: 1877 | Statement: [Richmond Underground station, openedForDistrictLine, 1877]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForDistrictLine Context triple: [Richmond Underground station, openedForDistrictLine, 1877]
-
A.
openedForServiceOnLine
chosen
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service line.
-
B.
openedAsRedLineStation
Indicates that a station began operation specifically as part of the Red Line when it first opened.
-
C.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
D.
openedAsMetrolinkLine
Indicates that a railway line or route was inaugurated or began operation specifically as part of the Metrolink network.
-
E.
northLineExtensionOpeningDate
Indicates the date on which the extension of the North Line officially opened for service.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f5261481908d9bac8c43da5294 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.