Triple

T12144063
Position Surface form Disambiguated ID Type / Status
Subject Ringvaart of the Haarlemmermeer E289269 entity
Predicate adjacentTo P224 FINISHED
Object Hoofddorp NE NERFINISHED

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: Hoofddorp | Statement: [Ringvaart of the Haarlemmermeer, adjacentTo, Hoofddorp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoofddorp
Context triple: [Ringvaart of the Haarlemmermeer, adjacentTo, Hoofddorp]
  • A. Hoofddorp chosen
    Hoofddorp is the main town and administrative center of the municipality of Haarlemmermeer in the Netherlands.
  • B. Zoetermeer
    Zoetermeer is a modern, rapidly grown satellite city of The Hague in the western Netherlands, known for its residential neighborhoods and light-rail connections.
  • C. Leidschendam-Voorburg
    Leidschendam-Voorburg is a municipality in the western Netherlands, near The Hague, formed by the towns of Leidschendam and Voorburg.
  • D. Oisterwijk
    Oisterwijk is a town in the Dutch province of North Brabant known for its historic center and surrounding forest and fen landscapes.
  • E. Houten
    Houten is a Dutch town in the province of Utrecht, known for its bicycle-friendly urban design and as the home of the Royal Dutch Mint.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915aacaa08190b31f54e230334406 completed April 10, 2026, 3:22 p.m.
Created at: April 8, 2026, 9:49 p.m.