Triple
T31539298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry II, Duke of Bavaria |
E804699
|
entity |
| Predicate | soughtThroneOf |
P171949
|
FINISHED |
| Object | Holy Roman Empire |
—
|
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: Holy Roman Empire | Statement: [Henry II, Duke of Bavaria, soughtThroneOf, Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtThroneOf Context triple: [Henry II, Duke of Bavaria, soughtThroneOf, Holy Roman Empire]
-
A.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
B.
linkedToThroneOf
Indicates a relationship where an entity is connected or related to a specific throne, typically through authority, succession, or symbolic association.
-
C.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
D.
throneName
Indicates the official royal or regnal name adopted by a ruler when they ascend to the throne.
-
E.
acceptedThrone
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
- F. None of above. chosen
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:05 p.m.