Triple

T22806609
Position Surface form Disambiguated ID Type / Status
Subject Forchbahn E564552 entity
Predicate servesMunicipality P3936 FINISHED
Object Maur 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: Maur | Statement: [Forchbahn, servesMunicipality, Maur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maur
Context triple: [Forchbahn, servesMunicipality, Maur]
  • A. Maur chosen
    Maur is a municipality in the canton of Zürich in Switzerland, located on the northeastern shore of Lake Greifen and known for its residential character and natural surroundings.
  • B. Maurin
    Maurin is a French surname most notably associated with Peter Maurin, the co-founder of the Catholic Worker Movement.
  • C. Mau
    Mau is a city in the Purvanchal region of eastern Uttar Pradesh, India, known for its textile and power-loom industry.
  • D. Maurik
    Maurik is a village in the Dutch province of Gelderland, known for its location along the Rhine and its recreational lakes.
  • E. MAUR
    MAUR is the Management Authority for Urban Railways, a government body responsible for overseeing the development and operation of urban rail transit systems.
  • 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_69e245823f4c8190ade442cdcc2c224a completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17d5c193481908550993e2547515d completed April 29, 2026, 3:39 a.m.
Created at: April 17, 2026, 3:32 p.m.