Triple
T4313819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiel |
E94139
|
entity |
| Predicate | locatedInRegion |
P40
|
FINISHED |
| Object | Betuwe |
E236999
|
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: Betuwe | Statement: [Tiel, locatedInRegion, Betuwe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Betuwe Context triple: [Tiel, locatedInRegion, Betuwe]
-
A.
Betuwe
chosen
Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
-
B.
Nissewaard
Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
-
C.
Hansweert
Hansweert is a small village in the Dutch province of Zeeland, known historically as a canal and shipping hub along the Western Scheldt.
-
D.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
-
E.
Vollenhove
Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f319c08190bb40a9fc5933728d |
completed | March 12, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fa512324819092e3a0b449cdb9ba |
completed | March 28, 2026, 3:57 p.m. |
Created at: March 12, 2026, 11:12 p.m.