Triple
T21728221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neunkirchen District |
E536328
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object |
Altendorf
Altendorf is a small municipality located in the Neunkirchen District of Lower Austria, known for its rural character and local agricultural landscape.
|
E1556210
|
NE FINISHED |
How this triple was built (4 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: Altendorf | Statement: [Neunkirchen District, hasMunicipality, Altendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Altendorf Context triple: [Neunkirchen District, hasMunicipality, Altendorf]
-
A.
Altendorf
Altendorf is a Swiss municipality in the canton of Schwyz, situated on the upper shores of Lake Zurich.
-
B.
Allendorf
Allendorf is a village-level subdivision of the town of Sundern in the Hochsauerland district of North Rhine-Westphalia, Germany.
-
C.
Asendorf
Asendorf is a small municipality in Lower Saxony, Germany, known for its rural character and location within the Diepholz district.
-
D.
Aulendorf
Aulendorf is a small town in the Upper Swabia region of southern Germany, known for its historic castle and spa facilities.
-
E.
Adendorf
Adendorf is a village-sized district within the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Altendorf Triple: [Neunkirchen District, hasMunicipality, Altendorf]
Generated description
Altendorf is a small municipality located in the Neunkirchen District of Lower Austria, known for its rural character and local agricultural landscape.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Altendorf Target entity description: Altendorf is a small municipality located in the Neunkirchen District of Lower Austria, known for its rural character and local agricultural landscape.
-
A.
Altendorf
Altendorf is a Swiss municipality in the canton of Schwyz, situated on the upper shores of Lake Zurich.
-
B.
Allendorf
Allendorf is a village-level subdivision of the town of Sundern in the Hochsauerland district of North Rhine-Westphalia, Germany.
-
C.
Asendorf
Asendorf is a small municipality in Lower Saxony, Germany, known for its rural character and location within the Diepholz district.
-
D.
Aulendorf
Aulendorf is a small town in the Upper Swabia region of southern Germany, known for its historic castle and spa facilities.
-
E.
Adendorf
Adendorf is a village-sized district within the municipality of Wachtberg in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
- F. None of above. chosen
Provenance (5 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd03c6ec8190a2f0445c1f3a45b4 |
completed | April 28, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ba791d9ec81908a518673ed3dd04b |
completed | May 18, 2026, 11:58 p.m. |
| NEDg | Description generation | batch_6a0ba81bade88190bc0f4225600509a2 |
completed | May 19, 2026, midnight |
| NED2 | Entity disambiguation (via description) | batch_6a0ba8c3d6c88190944df9358dd58c4e |
completed | May 19, 2026, 12:03 a.m. |
Created at: April 16, 2026, 6:48 p.m.