Triple
T5243210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soesterberg |
E118394
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Zeist |
E691289
|
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: Zeist | Statement: [Soesterberg, locatedNear, Zeist]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zeist Context triple: [Soesterberg, locatedNear, Zeist]
-
A.
Zeist
chosen
Zeist is a Dutch town and municipality in the central Netherlands known for its historic estates, green surroundings, and proximity to the city of Utrecht.
-
B.
Steenwijk
Steenwijk is a historic town in the Dutch province of Overijssel, known for its medieval center and role as a regional hub in the north of the province.
-
C.
Zoeterwoude
Zoeterwoude is a small Dutch municipality and village known for its rural character and location near Leiden in the province of South Holland.
-
D.
Oisterwijk
Oisterwijk is a town in the Dutch province of North Brabant known for its historic center and surrounding forest and fen landscapes.
-
E.
Harderwijk
Harderwijk is a historic Dutch city known for its former Hanseatic trading role and scenic location on the shores of the Veluwemeer.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4da7308190856cdcee9cca41eb |
completed | March 20, 2026, 4:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f2802d74f081909c7af34bf266ae01 |
completed | April 29, 2026, 10:03 p.m. |
Created at: March 20, 2026, 1:49 p.m.