Triple

T4405062
Position Surface form Disambiguated ID Type / Status
Subject Weerribben-Wieden National Park E93710 entity
Predicate hasPart P35 FINISHED
Object De Wieden E432812 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: De Wieden | Statement: [Weerribben-Wieden National Park, hasPart, De Wieden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: De Wieden
Context triple: [Weerribben-Wieden National Park, hasPart, De Wieden]
  • A. De Wieden chosen
    De Wieden is a renowned wetland nature reserve in the Dutch province of Overijssel, known for its lakes, reed beds, and rich birdlife.
  • B. Schwansen
    Schwansen is a rural peninsula in northern Germany situated between the Schlei inlet and the Eckernförde Bay in the state of Schleswig-Holstein.
  • C. Wiesener
    Wiesener is a surname, likely of German origin, that serves as a variant spelling of the name Wiesner.
  • D. Subingen
    Subingen is a Swiss municipality located in the canton of Solothurn, known for its residential character and proximity to regional transport routes.
  • E. Woudenberg
    Woudenberg is a small Dutch municipality and town located in the central Netherlands.
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b35488d5b8819087370dd77249aefb completed March 13, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69b627eb49308190a6830cbc52ad45cf completed March 15, 2026, 3:30 a.m.
Created at: March 12, 2026, 11:28 p.m.