Triple
T13096100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaica Station (LIRR) |
E310591
|
entity |
| Predicate | openedAsRailFacility |
P1712
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Jamaica Station (LIRR), openedAsRailFacility, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRailFacility Context triple: [Jamaica Station (LIRR), openedAsRailFacility, 19th century]
-
A.
openedAsRailStop
chosen
Indicates that an entity began operation or was first established specifically as a railway stop.
-
B.
openedAsRailroad
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
-
C.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
D.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
E.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.