Triple

T17948643
Position Surface form Disambiguated ID Type / Status
Subject Eemsdelta E448769 entity
Predicate containsSettlement P847 FINISHED
Object Wagenborgen 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: Wagenborgen | Statement: [Eemsdelta, containsSettlement, Wagenborgen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wagenborgen
Context triple: [Eemsdelta, containsSettlement, Wagenborgen]
  • A. Wagenborgen chosen
    Wagenborgen is a village in the Dutch province of Groningen, located within the municipality of Eemsdelta.
  • B. Wanneperveen
    Wanneperveen is a rural village in the Dutch province of Overijssel, known for its lakes, peat landscapes, and water-based recreation.
  • C. Wassenberg
    Wassenberg is a historic town in western Germany near the Dutch border, known for its medieval origins and association with the noble House of Wassenberg.
  • D. Wimsen
    Wimsen is a small settlement in the Swabian Jura region of Baden-Württemberg, Germany, known for its proximity to the Wimsener Höhle cave.
  • E. Wolthusen
    Wolthusen is a district of the seaport city of Emden in Lower Saxony, Germany, known for its residential character and proximity to the Ems estuary.
  • 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afaac780819097434b20b1f155d2 completed April 19, 2026, 10:34 a.m.
Created at: April 10, 2026, 10:21 a.m.