Triple
T28933582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont, Bronx |
E733852
|
entity |
| Predicate | servedBySubwayNearby |
P169742
|
FINISHED |
| Object | Fordham Road (B, D) stations |
—
|
NE NERFINISHED |
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: Fordham Road (B, D) stations | Statement: [Belmont, Bronx, servedBySubwayNearby, Fordham Road (B, D) stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedBySubwayNearby Context triple: [Belmont, Bronx, servedBySubwayNearby, Fordham Road (B, D) stations]
-
A.
subwayServiceAtNearbyStation
chosen
Indicates that there is subway service available at a station located near the referenced place or entity.
-
B.
subwayStationsApprox
Indicates that one subway station is approximately located near or corresponds to another subway station, allowing for minor differences in position or naming.
-
C.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
D.
nearMetroStation
Indicates that one entity is located close to or within a short walking distance of a metro (subway) station.
-
E.
hasUndergroundFeatureNearby
Indicates that an entity is located close to an underground feature (such as a tunnel, cave, or buried structure).
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 28, 2026, 8:30 a.m.