Triple
T34872904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fordham Road–Pelham Parkway corridor |
E1005798
|
entity |
| Predicate | hasBusRouteAlong |
P86982
|
FINISHED |
| Object | Bx12 |
—
|
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: Bx12 | Statement: [Fordham Road–Pelham Parkway corridor, hasBusRouteAlong, Bx12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusRouteAlong Context triple: [Fordham Road–Pelham Parkway corridor, hasBusRouteAlong, Bx12]
-
A.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
B.
situatedOnTransportRoute
chosen
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
C.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasTrolleybusLine
Indicates that there exists a trolleybus service or route connecting the related 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4 p.m.