Triple

T343083
Position Surface form Disambiguated ID Type / Status
Subject Muni E6878 entity
Predicate publicTransportNetwork P8428 FINISHED
Object San Francisco public transportation network 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: San Francisco public transportation network | Statement: [Muni, publicTransportNetwork, San Francisco public transportation network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicTransportNetwork
Context triple: [Muni, publicTransportNetwork, San Francisco public transportation network]
  • A. partOfTransitSystem chosen
    Indicates that something is a component or segment within a larger transit or transportation system.
  • B. publicTransit
    Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
  • C. busSystemName
    Indicates that a bus system is identified or referred to by a specific name.
  • D. publicTransportStatus
    Indicates the current operational condition or availability of a public transportation service or route.
  • 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_69a2e7951ba08190960e90823b5078f3 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eb0019088190a9b969c4287dc4fa completed Feb. 28, 2026, 1:17 p.m.
PD Predicate disambiguation batch_69a2e9530c98819085025efe4e04aa7e completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.