Triple

T3351335
Position Surface form Disambiguated ID Type / Status
Subject Lansingerland E70498 entity
Predicate borderedBy P224 FINISHED
Object Pijnacker-Nootdorp E187151 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: Pijnacker-Nootdorp | Statement: [Lansingerland, borderedBy, Pijnacker-Nootdorp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pijnacker-Nootdorp
Context triple: [Lansingerland, borderedBy, Pijnacker-Nootdorp]
  • A. Pijnacker-Nootdorp chosen
    Pijnacker-Nootdorp is a Dutch municipality in the western Netherlands, situated between The Hague and Rotterdam.
  • B. Zwijndrecht
    Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
  • C. Bloemendaal
    Bloemendaal is a coastal municipality in North Holland, Netherlands, known for its beaches, dunes, and affluent residential areas.
  • D. Nieuwendijk
    Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
  • E. Bodegraven-Reeuwijk
    Bodegraven-Reeuwijk is a Dutch municipality known for its rural landscapes, waterways, and cheese-producing heritage in the western Netherlands.
  • 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_69c787e303108190ab14b67c338b1377 completed March 28, 2026, 7:48 a.m.
Created at: March 8, 2026, 3:12 p.m.