Triple
T13826171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Reuss Younger Line |
E332253
|
entity |
| Predicate | predecessorState |
P10077
|
FINISHED |
| Object | Reuss-Ebersdorf |
E527608
|
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: Reuss-Ebersdorf | Statement: [Principality of Reuss Younger Line, predecessorState, Reuss-Ebersdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reuss-Ebersdorf Context triple: [Principality of Reuss Younger Line, predecessorState, Reuss-Ebersdorf]
-
A.
Reuss-Ebersdorf
chosen
Reuss-Ebersdorf was a small historical German principality ruled by a branch of the House of Reuss within the Holy Roman Empire and its successor states.
-
B.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
-
C.
Meisenbühl
Meisenbühl is a locality or neighborhood that forms part of the municipality of Oberkirch.
-
D.
Siegsdorf
Siegsdorf is a Bavarian town in southeastern Germany known for its scenic Alpine surroundings and proximity to the Chiemsee lake.
-
E.
Lorsbach
Lorsbach is a district of the town Hofheim am Taunus in the German state of Hesse, situated in the Taunus mountain region.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0295d2d48190b08eba0d805bd72d |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6474da3081909be6b892ef8cc73e |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 9, 2026, 10:13 p.m.