Triple
T8037701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pijnacker-Nootdorp |
E187151
|
entity |
| Predicate | formedByMergerOf |
P77
|
FINISHED |
| Object | Pijnacker |
E709235
|
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 | Statement: [Pijnacker-Nootdorp, formedByMergerOf, Pijnacker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pijnacker Context triple: [Pijnacker-Nootdorp, formedByMergerOf, Pijnacker]
-
A.
Pijnacker
chosen
Pijnacker is a town in the Dutch province of South Holland, known as a suburban community situated between The Hague and Rotterdam.
-
B.
Passewaaij
Passewaaij is a residential neighborhood of the Dutch city of Tiel, located in the province of Gelderland.
-
C.
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.
-
D.
Noordwyk
Noordwyk is a residential suburb located within the Midrand area of Johannesburg, South Africa.
-
E.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f19a6b4819085e2887fb0c54d08 |
completed | March 31, 2026, 3:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93bc11108190a34a35d0022f4bfd |
completed | April 1, 2026, 3:40 a.m. |
Created at: March 30, 2026, 5:23 p.m.