Triple
T23292768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drentsche Aa |
E590076
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Gasteren |
—
|
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: Gasteren | Statement: [Drentsche Aa, hasNearbySettlement, Gasteren]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gasteren Context triple: [Drentsche Aa, hasNearbySettlement, Gasteren]
-
A.
Gasteren
chosen
Gasteren is a small village in the Dutch province of Drenthe, known for its rural landscape and nearby prehistoric sites such as dolmens.
-
B.
Steggerda
Steggerda is a small village in the municipality of Weststellingwerf in the province of Friesland in the northern Netherlands.
-
C.
Dentergem
Dentergem is a municipality in the Belgian province of West Flanders.
-
D.
Beringen
Beringen is a city and municipality in the Belgian province of Limburg, known for its coal mining heritage and the be-MINE industrial heritage site.
-
E.
Beringen
Beringen is a municipality in northern Switzerland known for its location near the Rhine and its surrounding vineyards and rural landscapes.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cc20c08190a6a678befe1061dd |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:02 p.m.