Triple

T15501803
Position Surface form Disambiguated ID Type / Status
Subject N205 (Drie Merenweg) E378975 entity
Predicate connectsSettlement P8239 FINISHED
Object Vijfhuizen E78033 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: Vijfhuizen | Statement: [N205 (Drie Merenweg), connectsSettlement, Vijfhuizen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vijfhuizen
Context triple: [N205 (Drie Merenweg), connectsSettlement, Vijfhuizen]
  • A. Vijfhuizen chosen
    Vijfhuizen is a village in the Dutch province of North Holland, situated within the municipality of Haarlemmermeer near Haarlem.
  • B. Zevenhuizen
    Zevenhuizen is a village in the Dutch province of South Holland, known for its rural character and proximity to the city of Rotterdam.
  • C. Zevenhuizen
    Zevenhuizen is a village in the Dutch province of Groningen, located within the municipality of Westerkwartier.
  • D. Oldenzaal
    Oldenzaal is a historic city in the eastern Netherlands known for its medieval center and location near the German border in the province of Overijssel.
  • E. Hornhuizen
    Hornhuizen is a small village in the province of Groningen in the northern Netherlands, known for its rural landscape and historic church.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fcc5bb88190b8a9a81419a9a38b completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbba9fb08190b800af317f0c9abf completed May 10, 2026, 1:13 a.m.
Created at: April 10, 2026, 3:54 a.m.