Triple

T15346158
Position Surface form Disambiguated ID Type / Status
Subject Hoeksche Waard E366923 entity
Predicate containsSettlement P847 FINISHED
Object ’s-Gravendeel E1086284 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: ’s-Gravendeel | Statement: [Hoeksche Waard, containsSettlement, ’s-Gravendeel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ’s-Gravendeel
Context triple: [Hoeksche Waard, containsSettlement, ’s-Gravendeel]
  • A. ’s-Gravendeel chosen
    ’s-Gravendeel is a village in the South Holland province of the Netherlands, historically known as a polder settlement in the Hoeksche Waard region.
  • B. Legmeer
    Legmeer is a residential neighborhood within the Dutch municipality of Uithoorn in the province of North Holland.
  • C. Drost
    Drost is a Dutch surname most notably associated with the 17th-century painter Willem Drost, a pupil of Rembrandt.
  • D. Gwathmey
    Gwathmey is the surname of Charles Gwathmey, a prominent American architect known for his influential modernist designs.
  • E. Essenrode
    Essenrode is a small village in Lower Saxony, Germany, historically associated with the noble von Hardenberg family.
  • 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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e1749bc8190a8b9cbcb27288a5b completed April 16, 2026, 1:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff01f931408190828d87567cecaceb completed May 9, 2026, 9:44 a.m.
Created at: April 10, 2026, 3:17 a.m.