Triple

T3351401
Position Surface form Disambiguated ID Type / Status
Subject Voorschoten E70500 entity
Predicate borderedBy P224 FINISHED
Object Leidschendam-Voorburg E185969 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: Leidschendam-Voorburg | Statement: [Voorschoten, borderedBy, Leidschendam-Voorburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leidschendam-Voorburg
Context triple: [Voorschoten, borderedBy, Leidschendam-Voorburg]
  • A. Leidschendam-Voorburg chosen
    Leidschendam-Voorburg is a municipality in the western Netherlands, near The Hague, formed by the towns of Leidschendam and Voorburg.
  • B. Hoofddorp
    Hoofddorp is the main town and administrative center of the municipality of Haarlemmermeer in the Netherlands.
  • C. 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.
  • D. Zoeterwoude
    Zoeterwoude is a small Dutch municipality and village known for its rural character and location near Leiden in the province of South Holland.
  • E. Vlaardingen
    Vlaardingen is a historic port city in the western Netherlands, situated along the Nieuwe Maas river and known for its former herring fishing industry.
  • 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_69ad85a4ef7c8190a29e2bbd6fa454e4 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb220721c81909eb4d8d35c923927 completed March 8, 2026, 5:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c9d13a8b108190a0b13592f3a6362e completed March 30, 2026, 1:26 a.m.
Created at: March 8, 2026, 3:12 p.m.