Triple
T26927247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East New York station |
E678112
|
entity |
| Predicate | hasNearbySubwayLines |
P33788
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [East New York station, hasNearbySubwayLines, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySubwayLines Context triple: [East New York station, hasNearbySubwayLines, A]
-
A.
hasSubwayLineAboveOrBelow
Indicates that one subway line is physically located above or below another subway line, such as on different levels of a transit system.
-
B.
subwayServiceAtNearbyStation
Indicates that there is subway service available at a station located near the referenced place or entity.
-
C.
hasNearbyUndergroundStationEntrance
Indicates that one entity is located close to an entrance of an underground (subway/metro) station.
-
D.
nearUndergroundLine
chosen
Indicates that one entity is located close in distance to an underground (subway/metro) line.
-
E.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 6:10 a.m.