Triple
T23028168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lannesdorf |
E573380
|
entity |
| Predicate | hasNeighbouringDistrict |
P17964
|
FINISHED |
| Object | Rüngsdorf |
—
|
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: Rüngsdorf | Statement: [Lannesdorf, hasNeighbouringDistrict, Rüngsdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rüngsdorf Context triple: [Lannesdorf, hasNeighbouringDistrict, Rüngsdorf]
-
A.
Rüngsdorf
chosen
Rüngsdorf is a residential district in the southern part of Bonn, Germany, known for its scenic location along the Rhine and its affiliation with the Bad Godesberg borough.
-
B.
Rangsdorf
Rangsdorf is a municipality in the German state of Brandenburg, known for its lakeside setting and proximity to Berlin.
-
C.
Ronsdorf
Ronsdorf is a district of the German city of Wuppertal in North Rhine-Westphalia, historically known as an independent town in the Bergisches Land region.
-
D.
Wietzendorf
Wietzendorf is a small municipality in Lower Saxony, Germany, known for its rural character and location in the Lüneburg Heath region.
-
E.
Ruppersdorf
Ruppersdorf is a small locality in Germany, historically part of East Prussia, known as the birthplace of German general Otto Lasch.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847f453881909a8f2affb48c64f1 |
completed | April 29, 2026, 4:09 a.m. |
Created at: April 17, 2026, 3:52 p.m.