Triple
T22016038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leiden region |
E543711
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Voorschoten |
—
|
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: Voorschoten | Statement: [Leiden region, hasPart, Voorschoten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Voorschoten Context triple: [Leiden region, hasPart, Voorschoten]
-
A.
Voorschoten
chosen
Voorschoten is a town and municipality in the western Netherlands, situated between The Hague and Leiden and known for its residential character and historic village center.
-
B.
Toekomsrus
Toekomsrus is a township within the Rand West City Local Municipality in Gauteng, South Africa.
-
C.
Uitweg
Uitweg is a small village in the Dutch province of Utrecht, located within the municipality of Lopik.
-
D.
Overloon
Overloon is a village in the Dutch province of North Brabant, best known for its World War II history and the Overloon War Museum.
-
E.
Leende
Leende is a village in the Dutch province of North Brabant, historically part of the baronial estate of Heeze, Leende and Zesgehuchten.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a8a1388190b9e0c1795fe1183a |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:22 p.m.