Triple
T23222696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schouwen-Duiveland |
E580934
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Dreischor |
E457679
|
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: Dreischor | Statement: [Schouwen-Duiveland, containsSettlement, Dreischor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dreischor Context triple: [Schouwen-Duiveland, containsSettlement, Dreischor]
-
A.
Dreischor
chosen
Dreischor is a historic village in the Dutch province of Zeeland, known for its well-preserved ring-shaped layout and traditional architecture.
-
B.
Löhr
Löhr is a German-language surname borne by various notable individuals, including figures in military, arts, and public life.
-
C.
Schwerteck
Schwerteck is a mountain peak in the Glockner Group of the Austrian Alps.
-
D.
Oberdrees
Oberdrees is a village-level district of the town of Rheinbach in the Rhein-Sieg-Kreis of North Rhine-Westphalia, Germany.
-
E.
Eichelbaum
Eichelbaum is a German-language surname borne by various individuals, including figures in law, arts, and public life.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922a452c81909b48df157643f6bd |
completed | April 29, 2026, 5:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c30ce65b48190a621f67a75b84fea |
completed | May 19, 2026, 9:43 a.m. |
Created at: April 17, 2026, 4:08 p.m.