Triple
T6644750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RapidRide |
E150672
|
entity |
| Predicate | servesCorridors |
P2566
|
FINISHED |
| Object | major transportation corridors |
—
|
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: major transportation corridors | Statement: [RapidRide, servesCorridors, major transportation corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCorridors Context triple: [RapidRide, servesCorridors, major transportation corridors]
-
A.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
B.
numberOfCorridors
Indicates the total count of corridors associated with or contained within a given entity or structure.
-
C.
hasServiceOnCorridor
chosen
Indicates that a service operates along, or is provided on, a specific corridor or route.
-
D.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
E.
isMostHeavilyTraveledCorridorIn
Indicates that a particular route or corridor experiences the highest volume of travel or traffic within a specified area or region.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.