Triple

T3645055
Position Surface form Disambiguated ID Type / Status
Subject Lijnden E77278 entity
Predicate locatedNear P294 FINISHED
Object Zwanenburg E270652 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: Zwanenburg | Statement: [Lijnden, locatedNear, Zwanenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zwanenburg
Context triple: [Lijnden, locatedNear, Zwanenburg]
  • A. Rozenburg
    Rozenburg is a town in the western Netherlands that forms part of the heavily industrialized and port-dominated region of South Holland.
  • B. Rozenburg chosen
    Rozenburg is a village in the municipality of Haarlemmermeer in the province of North Holland, Netherlands.
  • C. Goudswaard
    Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • D. Winschoten
    Winschoten is a town in the northeast of the Netherlands known historically as a regional trade center and for its traditional windmills and Jewish heritage.
  • E. Nissewaard
    Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
  • 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_69ad85de1b988190a45f8dbfebc806fc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc35da84c81908950de92ba171fa3 completed March 8, 2026, 6:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f0989c88190b4c675c7a6ec0e3e completed March 14, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:24 p.m.