Triple
T8742752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City public transportation network |
E207542
|
entity |
| Predicate | busRoutesApprox |
P73415
|
FINISHED |
| Object | over 300 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: over 300 bus routes | Statement: [New York City public transportation network, busRoutesApprox, over 300 bus routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busRoutesApprox Context triple: [New York City public transportation network, busRoutesApprox, over 300 bus routes]
-
A.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
B.
providesUrbanTransport
chosen
Indicates that one entity supplies or operates transportation services within an urban or city environment for another entity or the public.
-
C.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
-
D.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
E.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d71619481909fc4d87af3d01432 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.