Triple

T13635346
Position Surface form Disambiguated ID Type / Status
Subject Greater Zürich Area E325833 entity
Predicate includesMunicipality P14658 FINISHED
Object Opfikon E500649 NE 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: Opfikon | Statement: [Greater Zürich Area, includesMunicipality, Opfikon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opfikon
Context triple: [Greater Zürich Area, includesMunicipality, Opfikon]
  • A. Opfikon chosen
    Opfikon is a municipality in the canton of Zürich in Switzerland, known for its proximity to Zurich Airport and its role as a residential and commercial suburb of the city of Zürich.
  • B. Rüschlikon
    Rüschlikon is a wealthy lakeside municipality on the western shore of Lake Zurich in the canton of Zurich, Switzerland.
  • C. Hinwil
    Hinwil is a municipality and regional center in the Swiss canton of Zürich, known for its rural surroundings and as the home base of the Sauber Formula One team.
  • D. Kloten
    Kloten is a town in the canton of Zurich in northern Switzerland, best known as the home of Zurich Airport.
  • E. Pfäffikon SZ
    Pfäffikon SZ is a town in the Swiss canton of Schwyz on the shores of Lake Zurich, known as a regional economic center and tax-favorable residential area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8076beddc8190a53156f5bea77f5e completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc5a616dc81908b8c1213e1d4beed completed April 12, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd27f43bf081908dea65dc05f7c1a2 completed May 8, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:51 p.m.