Triple
T15247051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Tucher |
E364409
|
entity |
| Predicate | hasEstate |
P8997
|
FINISHED |
| Object |
Simmelsdorf
Simmelsdorf is a municipality in the district of Nürnberger Land in Bavaria, Germany, known for its rural character and historic Franconian architecture.
|
E1166226
|
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: Simmelsdorf | Statement: [von Tucher, hasEstate, Simmelsdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Simmelsdorf Context triple: [von Tucher, hasEstate, Simmelsdorf]
-
A.
Seifhennersdorf
Seifhennersdorf is a small town in the Görlitz district of Saxony in eastern Germany, near the Czech border.
-
B.
Gimmersdorf
Gimmersdorf is a small village that forms one of the local subdivisions of the municipality of Wachtberg in Germany.
-
C.
Oberwaltersdorf
Oberwaltersdorf is a municipality in Lower Austria known for its residential character, proximity to Vienna, and local wine-growing and leisure facilities.
-
D.
Rannersdorf
Rannersdorf is a village and cadastral community that forms part of the town of Schwechat in Lower Austria, near Vienna.
-
E.
Emsdorf
Emsdorf is a village in the German state of Hesse, historically notable as the site of the Battle of Emsdorf during the Seven Years' War.
- 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: Simmelsdorf Triple: [von Tucher, hasEstate, Simmelsdorf]
Generated description
Simmelsdorf is a municipality in the district of Nürnberger Land in Bavaria, Germany, known for its rural character and historic Franconian architecture.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Simmelsdorf Target entity description: Simmelsdorf is a municipality in the district of Nürnberger Land in Bavaria, Germany, known for its rural character and historic Franconian architecture.
-
A.
Seifhennersdorf
Seifhennersdorf is a small town in the Görlitz district of Saxony in eastern Germany, near the Czech border.
-
B.
Gimmersdorf
Gimmersdorf is a small village that forms one of the local subdivisions of the municipality of Wachtberg in Germany.
-
C.
Oberwaltersdorf
Oberwaltersdorf is a municipality in Lower Austria known for its residential character, proximity to Vienna, and local wine-growing and leisure facilities.
-
D.
Rannersdorf
Rannersdorf is a village and cadastral community that forms part of the town of Schwechat in Lower Austria, near Vienna.
-
E.
Emsdorf
Emsdorf is a village in the German state of Hesse, historically notable as the site of the Battle of Emsdorf during the Seven Years' War.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f4f9d48190b96a7e0c6993cd69 |
completed | April 15, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff56b25a808190b56f8ab3c506b771 |
completed | May 9, 2026, 3:45 p.m. |
| NEDg | Description generation | batch_69ff5844ba34819088ec15a0ba87d2cd |
completed | May 9, 2026, 3:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff589de85c8190abc9c888ac90cf52 |
completed | May 9, 2026, 3:54 p.m. |
Created at: April 10, 2026, 3:13 a.m.