Triple

T16460058
Position Surface form Disambiguated ID Type / Status
Subject Köniz E399782 entity
Predicate hasSettlement P1068 FINISHED
Object Wabern E1182156 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: Wabern | Statement: [Köniz, hasSettlement, Wabern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wabern
Context triple: [Köniz, hasSettlement, Wabern]
  • A. Wabern chosen
    Wabern is a district of the municipality of Köniz near Bern in Switzerland, known for hosting various federal institutions and serving as a suburban residential area.
  • B. Wabern
    Wabern is a settlement located within the historical Province of Westphalia in Germany.
  • C. Meerbusch
    Meerbusch is a town in the German state of North Rhine-Westphalia, situated on the west bank of the Rhine near Düsseldorf and known for its affluent residential areas and green surroundings.
  • D. Scheyern
    Scheyern is a Bavarian municipality best known as the site of Scheyern Abbey, a historic Benedictine monastery and ancestral seat of the Wittelsbach family.
  • E. Riehe
    Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32d80e66c8190b2b3199efe9cfaa1 completed April 18, 2026, 7:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f53aff081909a75de6672f15f0e completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:10 a.m.