Triple
T23918808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A train (Rockaway branch) |
E602155
|
entity |
| Predicate | openedToRockaways |
P154361
|
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: [A train (Rockaway branch), openedToRockaways, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToRockaways Context triple: [A train (Rockaway branch), openedToRockaways, 1956]
-
A.
connectsRockawayParkTo
Indicates a relationship where something serves as a link or route between Rockaway Park and another place or entity.
-
B.
openedToBoston
Indicates that something was opened, initiated, or made accessible specifically toward or in the direction of Boston.
-
C.
openedAsNYCSubwayStation
Indicates that an entity began operation specifically as a New York City Subway station at the time it opened.
-
D.
openedAsPartOfNJTransit
Indicates that the subject entity was opened specifically as a component or facility of the NJ Transit system.
-
E.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1600248190b38cfc93afb22a73 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:41 p.m.