Triple
T26010783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry VI |
E646892
|
entity |
| Predicate | successor as Holy Roman Emperor |
P10608
|
FINISHED |
| Object | Otto IV |
—
|
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: Otto IV | Statement: [Henry VI, successor as Holy Roman Emperor, Otto IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successor as Holy Roman Emperor Context triple: [Henry VI, successor as Holy Roman Emperor, Otto IV]
-
A.
successorAsHolyRomanEmperor
chosen
Indicates that one entity directly follows another in holding the title of Holy Roman Emperor.
-
B.
successorAsKingOfTheRomans
Indicates that one person is the next holder of the title "King of the Romans" following another person in the line of succession.
-
C.
successorAsGermanEmperor
Indicates that one entity became the next holder of the title of German Emperor directly after another entity.
-
D.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
-
E.
reign as Holy Roman Emperor
Indicates that a person holds and exercises the ruling authority and title of Holy Roman Emperor during a specified period.
- F. None of above.
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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 22, 2026, 9:01 a.m.