Triple
T13825851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordinatio Imperii of 817 |
E332245
|
entity |
| Predicate | designatedTitleForLothair |
P78578
|
FINISHED |
| Object | emperor |
—
|
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: emperor | Statement: [Ordinatio Imperii of 817, designatedTitleForLothair, emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedTitleForLothair Context triple: [Ordinatio Imperii of 817, designatedTitleForLothair, emperor]
-
A.
successorInLotharingia
Indicates that one entity is the direct successor of another in ruling or holding authority over Lotharingia.
-
B.
commandingTitleOfCharlesMartel
Indicates that the object is a commanding or honorific title held by Charles Martel.
-
C.
successorAsKingOfWestFrancia
Indicates that one person became the next king of West Francia after another person, directly following them in that royal succession.
-
D.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
E.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0295d2d48190b08eba0d805bd72d |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.