Triple
T21180104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuss-Lobenstein |
E521923
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Reuss-Ebersdorf |
—
|
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: Reuss-Ebersdorf | Statement: [Reuss-Lobenstein, successor, Reuss-Ebersdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reuss-Ebersdorf Context triple: [Reuss-Lobenstein, successor, 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.
Ueberstorf
Ueberstorf is a municipality in the canton of Fribourg in western Switzerland, known for its rural character and location near the linguistic border between German- and French-speaking regions.
-
E.
Obergriesbach
Obergriesbach is a small municipality in the district of Aichach-Friedberg in the Bavarian region of Germany.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301c842c8190b969a8b3f194003a |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 3:01 p.m.