Triple
T28021047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosstown Local |
E707687
|
entity |
| Predicate | openedAsServiceOn |
P178781
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Crosstown Local, openedAsServiceOn, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsServiceOn Context triple: [Crosstown Local, openedAsServiceOn, 1933]
-
A.
openedFirstService
Indicates that one entity initiated or conducted the first instance of a particular service for another entity or in a given context.
-
B.
openedForServiceTo
Indicates that one entity has been made available or activated to provide service or functionality to another entity.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
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.
-
E.
openedForServiceOnLine
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service line.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 8:10 p.m.