Triple
T8182045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND 63rd Street Line |
E191084
|
entity |
| Predicate | fullServiceToQueensOpened |
P15151
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [IND 63rd Street Line, fullServiceToQueensOpened, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullServiceToQueensOpened Context triple: [IND 63rd Street Line, fullServiceToQueensOpened, 2001]
-
A.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
C.
mainVenueOpened
Indicates that the primary venue associated with an event or organization has begun operations or officially opened.
-
D.
openedForThroughService
chosen
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.
-
E.
openedAsMetraService
Indicates that a transportation facility or line began operating specifically as part of the Metra commuter rail 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4db8748190aa785e0c70fac497 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.