Triple

T15426263
Position Surface form Disambiguated ID Type / Status
Subject Biggekerke E369518 entity
Predicate nearbySettlement P350 FINISHED
Object Zoutelande E361426 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: Zoutelande | Statement: [Biggekerke, nearbySettlement, Zoutelande]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zoutelande
Context triple: [Biggekerke, nearbySettlement, Zoutelande]
  • A. Zoutelande chosen
    Zoutelande is a coastal village and popular seaside resort in the Dutch province of Zeeland, known for its beaches and dunes along the North Sea.
  • B. Maasland
    Maasland is a historical region in the Low Countries centered along the river Meuse, known for its medieval political and cultural significance.
  • C. Landsmeer
    Landsmeer is a small Dutch town and municipality in North Holland, situated just north of Amsterdam and known for its watery landscapes and nature reserves.
  • D. Kennemerland
    Kennemerland is a coastal historical region in the northwest of the Netherlands, known for its dunes, beaches, and old trading towns.
  • E. Nederwaardse Boezem
    Nederwaardse Boezem is a Dutch polder waterway and drainage basin in the province of South Holland, known for its role in regional water management near the Lek River.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec1fb288190a3625b8e4f487dd1 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a8099448190be71f7b649c7e545 completed May 9, 2026, 11:29 a.m.
Created at: April 10, 2026, 3:20 a.m.