Triple

T4740060
Position Surface form Disambiguated ID Type / Status
Subject Stellendam E105216 entity
Predicate near P350 FINISHED
Object Middelharnis E70502 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: Middelharnis | Statement: [Stellendam, near, Middelharnis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Middelharnis
Context triple: [Stellendam, near, Middelharnis]
  • A. Middelharnis chosen
    Middelharnis is a town in the western Netherlands known historically as a fishing and agricultural community on the island of Goeree-Overflakkee.
  • B. Middelstum
    Middelstum is a historic village in the Dutch province of Groningen, known for its old churches and traditional architecture.
  • C. Danelaw
    Danelaw was a historical region of England under Scandinavian control and influence, characterized by Norse law, culture, and settlement during the early Middle Ages.
  • D. Ludbreg
    Ludbreg is a small historic town in northern Croatia, often noted for its religious heritage and claim to be the geographic center of the country.
  • E. Oldambt
    Oldambt is a municipality in the northeast of the Netherlands, known for its reclaimed lake Oldambtmeer and its agricultural landscapes.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6486f8608190908e43b777810c44 completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a211d2c8190a87ad81ef90dcf3b completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:19 p.m.