Triple
T5610526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockaway Park Shuttle |
E147343
|
entity |
| Predicate | openedAsShuttle |
P6141
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Rockaway Park Shuttle, openedAsShuttle, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsShuttle Context triple: [Rockaway Park Shuttle, openedAsShuttle, 1956]
-
A.
openedAs
chosen
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
B.
openedToTransit
Indicates that a route, passage, or connection has been made available or accessible for transit or movement between locations.
-
C.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
D.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
E.
openedAsThroughRoute
Indicates that a route or service began operating as a continuous through connection, rather than as separate or terminating segments.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0211dfc88819097b6d4254a61f65a |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.