Triple
T16045174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Saxe-Hildburghausen |
E389197
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Hildburghausen |
E509978
|
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: Hildburghausen | Statement: [Duchy of Saxe-Hildburghausen, namedAfter, Hildburghausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hildburghausen Context triple: [Duchy of Saxe-Hildburghausen, namedAfter, Hildburghausen]
-
A.
Hildburghausen
chosen
Hildburghausen is a town in the German state of Thuringia that historically served as the residence of the dukes of Saxe-Hildburghausen.
-
B.
Gräfenhausen
Gräfenhausen is a district of the town of Weiterstadt in the state of Hesse, Germany.
-
C.
Haßfurt
Haßfurt is a small town in northern Bavaria, Germany, situated on the Main River and known for its historic architecture and regional administrative role.
-
D.
Rudolstadt
Rudolstadt is a historic town in the German state of Thuringia, known for its picturesque old town, Heidecksburg Castle, and cultural festivals.
-
E.
Altenstadt
Altenstadt is a small Bavarian municipality in southern Germany, situated within the rural district of Weilheim-Schongau.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1835d1dac819089abec9f0668ec78 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c790ec64819084277c156f38a7de |
completed | May 10, 2026, 5:59 p.m. |
Created at: April 10, 2026, 4:56 a.m.