Triple
T15634651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nister |
E375907
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Betzdorf |
E526649
|
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: Betzdorf | Statement: [Nister, flowsNear, Betzdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Betzdorf Context triple: [Nister, flowsNear, Betzdorf]
-
A.
Betzdorf
chosen
Betzdorf is a commune in eastern Luxembourg known for its residential areas, railway facilities, and the presence of Betzdorf Castle.
-
B.
Bergheim
Bergheim is a municipality in the Austrian state of Salzburg, located just north of the city of Salzburg and known for its suburban character and proximity to the regional capital.
-
C.
Bergheim
Bergheim is a town in western Germany situated along the Erft River, known for its historical center and proximity to the Cologne region.
-
D.
Diedorf
Diedorf is a market town in Bavaria, Germany, located just west of the city of Augsburg.
-
E.
Borsdorf
Borsdorf is a small municipality in the Leipzig district of Saxony, Germany, situated just east of Leipzig in a largely rural and suburban landscape.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb8b4c48190b80fea6877483089 |
completed | April 16, 2026, 2:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff79031f88190bf129582deeed3b9 |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 4:14 a.m.