Triple
T14087436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midden-Drenthe |
E339033
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Beilen |
E1080317
|
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: Beilen | Statement: [Midden-Drenthe, containsSettlement, Beilen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beilen Context triple: [Midden-Drenthe, containsSettlement, Beilen]
-
A.
Beilen
chosen
Beilen is a town in the Dutch province of Drenthe that serves as the administrative center of the municipality of Midden-Drenthe.
-
B.
Bielke
Bielke is the surname of a notable Swedish noble family historically associated with prominent political and military figures.
-
C.
Beuel
Beuel is a district on the right bank of the Rhine in the German city of Bonn, known for its residential areas and local carnival traditions.
-
D.
Schippenbeil
Schippenbeil is the former German name for the town now known as Sępopol in northeastern Poland.
-
E.
Ilkenau
Ilkenau is the historical German name for the Polish town of Olkusz, located in southern Poland.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdefe88b481908b3dca1f019e7809 |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:21 p.m.