Triple

T13467802
Position Surface form Disambiguated ID Type / Status
Subject North Beveland E311547 entity
Predicate containsSettlement P847 FINISHED
Object Colijnsplaat 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: Colijnsplaat | Statement: [North Beveland, containsSettlement, Colijnsplaat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Colijnsplaat
Context triple: [North Beveland, containsSettlement, Colijnsplaat]
  • A. Colijnsplaat chosen
    Colijnsplaat is a small coastal village in the Dutch province of Zeeland, known for its fishing harbor and scenic location on the Oosterschelde estuary.
  • B. Zwijndrecht
    Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
  • C. Hulst
    Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
  • D. Slochteren
    Slochteren is a village and former municipality in the province of Groningen in the Netherlands, historically known for its large natural gas field.
  • E. Sittard
    Sittard is a historic city in the Dutch province of Limburg, known for its medieval center and proximity to the German and Belgian borders.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf101a1081909f2aba6da47baacc completed April 12, 2026, 2:41 p.m.
Created at: April 9, 2026, 9:42 p.m.