Triple

T14102163
Position Surface form Disambiguated ID Type / Status
Subject Bremgarten, Aargau, Switzerland E339409 entity
Predicate neighboringMunicipality P17964 FINISHED
Object Wohlen, Aargau E945299 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: Wohlen, Aargau | Statement: [Bremgarten, Aargau, Switzerland, neighboringMunicipality, Wohlen, Aargau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wohlen, Aargau
Context triple: [Bremgarten, Aargau, Switzerland, neighboringMunicipality, Wohlen, Aargau]
  • A. Wohlen bei Bern
    Wohlen bei Bern is a municipality in the canton of Bern, Switzerland, situated just north of the city of Bern within its metropolitan region.
  • B. Wohlen chosen
    Wohlen is a municipality and regional center in the Swiss canton of Aargau, known for its industrial history and role as a local economic hub.
  • C. Wädenswil
    Wädenswil is a Swiss town in the canton of Zurich known for its lakeside location, wine-growing tradition, and research institutes.
  • D. Walperswil
    Walperswil is a small municipality in the canton of Bern in Switzerland.
  • E. Veltheim (Aargau)
    Veltheim (Aargau) is a small Swiss municipality in the canton of Aargau, known for its rural character and location in the Aare river valley.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fbbf0b08190ba1ea3657d6db005 completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0b108908190b4b408f21ecb877a completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:22 p.m.