Triple

T22146430
Position Surface form Disambiguated ID Type / Status
Subject Van Ness station E547298 entity
Predicate hasConnection P8776 FINISHED
Object Muni trolleybus NE NERFINISHED

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: Muni trolleybus | Statement: [Van Ness station, hasConnection, Muni trolleybus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muni trolleybus
Context triple: [Van Ness station, hasConnection, Muni trolleybus]
  • A. Muni trolleybus chosen
    A Muni trolleybus is an electrically powered San Francisco Municipal Railway bus that draws power from overhead wires to provide zero-emission transit service on city streets.
  • B. Trolebús
    Trolebús is an electric trolleybus transit system serving Mexico City as part of its broader public transportation network.
  • C. Interurban Trolley
    Interurban Trolley is a regional bus system providing fixed-route public transportation service in and around Elkhart and Goshen in northern Indiana.
  • D. Commerce Municipal Bus
    Commerce Municipal Bus is the city-operated public bus system serving residents, workers, and visitors in Commerce, California.
  • E. Lucerne trolleybuses
    Lucerne trolleybuses are an electric trolleybus network forming a key component of the public transport system in the Swiss city of Lucerne.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e3a95d88190a3bd80d9471976c3 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f097248190a8a3cdff1593b5b5 completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.