Triple
T36194586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R188 |
E1047086
|
entity |
| Predicate | enteredFullServiceOnLine |
P41908
|
FINISHED |
| Object | IRT Flushing Line |
—
|
NE NERFINISHED |
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: IRT Flushing Line | Statement: [R188, enteredFullServiceOnLine, IRT Flushing Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredFullServiceOnLine Context triple: [R188, enteredFullServiceOnLine, IRT Flushing Line]
-
A.
enteredServiceOnLine14
Indicates that an entity (such as a vehicle or piece of equipment) began operating in regular service on route or line 14.
-
B.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
-
C.
wentFullyOnline
Indicates that an entity transitioned from a non-online or partially online state to operating entirely online.
-
D.
openedForServiceOnLine
chosen
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service line.
-
E.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.