Triple
T29355319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Fordham Road |
E744424
|
entity |
| Predicate | hasTransitConnectionType |
P192554
|
FINISHED |
| Object | bus routes |
—
|
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: bus routes | Statement: [East Fordham Road, hasTransitConnectionType, bus routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransitConnectionType Context triple: [East Fordham Road, hasTransitConnectionType, bus routes]
-
A.
hasTransitServiceType
chosen
Indicates that a transit service is associated with a specific type or category of service (e.g., bus, rail, express).
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
hasPlannedTransportConnection
Indicates that there is an intended or scheduled transport link (e.g., route, service, or connection) planned to operate between the related entities.
-
D.
hasFareGateConnectionTo
Indicates that there is a direct passage or connection between two areas that is controlled or mediated by fare gates.
-
E.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 28, 2026, 2:11 p.m.