Triple
T11632243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutphin Boulevard–Archer Avenue–JFK Airport station |
E276425
|
entity |
| Predicate | fareZoneForLIRR |
P69645
|
FINISHED |
| Object | Zone 1 |
—
|
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: Zone 1 | Statement: [Sutphin Boulevard–Archer Avenue–JFK Airport station, fareZoneForLIRR, Zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneForLIRR Context triple: [Sutphin Boulevard–Archer Avenue–JFK Airport station, fareZoneForLIRR, Zone 1]
-
A.
servedByLIRRStation
Indicates that a location or facility is provided rail service by a Long Island Rail Road (LIRR) station.
-
B.
fareZoneDescription
Indicates the textual description of the fare zone associated with a service, location, or segment.
-
C.
fareZoneIncludes
chosen
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
D.
fareZoneStart
Indicates the fare zone in which a journey, ticket, or pricing calculation begins.
-
E.
fareZoneEnd
Indicates the ending boundary or final zone in a defined fare zone range for a trip or ticket.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.