Triple
T4468611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huis Doorn |
E98439
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Doorn |
E396839
|
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: Doorn | Statement: [Huis Doorn, locatedIn, Doorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Doorn Context triple: [Huis Doorn, locatedIn, Doorn]
-
A.
Doorn
chosen
Doorn is a village in the Dutch province of Utrecht, best known as the place where the exiled German Emperor Wilhelm II spent his final years and died.
-
B.
Valkenswaard
Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
-
C.
Deurne
Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
-
D.
Oosterhout
Oosterhout is a town and municipality in the southern Netherlands known for its historic monasteries and proximity to the city of Breda.
-
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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3569ba84881909e9c1d9dfc004439 |
completed | March 13, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74872582c81908c64a9bf925f67c6 |
completed | March 28, 2026, 3:18 a.m. |
Created at: March 12, 2026, 11:34 p.m.