Triple

T5607887
Position Surface form Disambiguated ID Type / Status
Subject Santa Rosa CityBus E147276 entity
Predicate hasRouteStructure P32810 FINISHED
Object radial routes centered on downtown Santa Rosa 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: radial routes centered on downtown Santa Rosa | Statement: [Santa Rosa CityBus, hasRouteStructure, radial routes centered on downtown Santa Rosa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRouteStructure
Context triple: [Santa Rosa CityBus, hasRouteStructure, radial routes centered on downtown Santa Rosa]
  • A. hasRoute
    Indicates that there exists a path or connection enabling travel or communication from one entity to another.
  • B. hasMajorStructureOnRoute
    Indicates that a significant physical structure is located along or directly associated with a particular route.
  • C. hasRouteType
    Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
  • D. routeStructure chosen
    Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
  • E. hasRouteFeature
    Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
  • 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_69c0090500f881908374285baf0ac46f completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020fd1b2c81908da154f7e11b90d8 completed March 22, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69c01b1b3c98819080687d18ab10a914 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:39 p.m.