Triple
T26010777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry VI |
E646892
|
entity |
| Predicate | coronation as Holy Roman Emperor |
P114470
|
FINISHED |
| Object | 1191 |
—
|
LITERAL 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: 1191 | Statement: [Henry VI, coronation as Holy Roman Emperor, 1191]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronation as Holy Roman Emperor Context triple: [Henry VI, coronation as Holy Roman Emperor, 1191]
-
A.
coronationAsKingOfTheRomans
Indicates the event in which a person is formally crowned and recognized as King of the Romans.
-
B.
coronationAsHolyRomanEmperorYear
chosen
Indicates the year in which an individual was crowned as Holy Roman Emperor.
-
C.
coronationPlaceAsHolyRomanEmperor
Indicates the place where a person was ceremonially crowned as Holy Roman Emperor.
-
D.
crownedHolyRomanEmperor
Indicates that a person has been formally invested with the title and authority of Holy Roman Emperor through a coronation ceremony.
-
E.
successorAsGermanEmperor
Indicates that one entity became the next holder of the title of German Emperor directly after another entity.
- 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_69f605b4fa288190981533f604eea508 |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:01 a.m.