Triple
T10172329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baden District |
E235360
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Teesdorf |
E790602
|
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: Teesdorf | Statement: [Baden District, contains, Teesdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teesdorf Context triple: [Baden District, contains, Teesdorf]
-
A.
Teesdorf
chosen
Teesdorf is a municipality in Lower Austria known for its motorsport testing facilities and rural setting south of Vienna.
-
B.
Ruppersdorf
Ruppersdorf is a small locality in Germany, historically part of East Prussia, known as the birthplace of German general Otto Lasch.
-
C.
Degendorf
Degendorf is a locality within the Bavarian town and district of Lichtenfels in Germany.
-
D.
Friedrichsdorf
Friedrichsdorf is a town in the German state of Hesse, located north of Frankfurt and known historically for its Huguenot heritage and proximity to the Taunus mountains.
-
E.
Wilhelmsdorf
Wilhelmsdorf is a village-level subdivision of the town of Usingen in the Hochtaunus district of Hesse, Germany.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9f6dd8819081588600499165ee |
completed | April 2, 2026, 4:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3178844c48190af952ac30a4d6d97 |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:10 p.m.