Triple

T9920037
Position Surface form Disambiguated ID Type / Status
Subject Leidschendam-Voorburg E185969 entity
Predicate hasVillage P4011 FINISHED
Object Stompwijk E866733 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: Stompwijk | Statement: [Leidschendam-Voorburg, hasVillage, Stompwijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stompwijk
Context triple: [Leidschendam-Voorburg, hasVillage, Stompwijk]
  • A. Stompwijk chosen
    Stompwijk is a village in the Dutch province of South Holland, known for its rural character and location within the municipality of Leidschendam-Voorburg.
  • B. Westwijk
    Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
  • C. Bullewijk
    Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
  • D. Passewaaij
    Passewaaij is a residential neighborhood of the Dutch city of Tiel, located in the province of Gelderland.
  • E. Nieuwendijk
    Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
  • 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_69ca829b45f481909040f7b99a1976ed completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb5699bc48190961e036d1131fef0 completed April 2, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69ee85e044e881909d426f7121dd89e1 completed April 26, 2026, 9:38 p.m.
Created at: March 30, 2026, 8:42 p.m.