Triple
T20571566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Sayn |
E505109
|
entity |
| Predicate | hasSeat |
P3522
|
FINISHED |
| Object | Hachenburg |
—
|
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: Hachenburg | Statement: [County of Sayn, hasSeat, Hachenburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hachenburg Context triple: [County of Sayn, hasSeat, Hachenburg]
-
A.
Hachenburg
chosen
Hachenburg is a historic small town in the Westerwald region of Rhineland-Palatinate, Germany, known for its medieval town center and hilltop castle.
-
B.
Schwanenburg
Schwanenburg is a historic hilltop castle in Kleve, Germany, known for its prominent tower and its role in regional medieval and early modern history.
-
C.
Langenhain
Langenhain is a district of the town Hofheim am Taunus in the German state of Hesse, known for its residential character and proximity to the Taunus hills.
-
D.
Hornsberg
Hornsberg is a waterfront residential and commercial district on the island of Kungsholmen in central Stockholm, Sweden.
-
E.
Hagsdorf
Hagsdorf is a small locality that forms part of the municipality of Persenbeug-Gottsdorf in Lower Austria.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a905b1288190bbad9aa14362bb97 |
completed | April 20, 2026, 10:30 p.m. |
Created at: April 16, 2026, 11:39 a.m.