Triple
T13825595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis I |
E332239
|
entity |
| Predicate | coronationAsEmperor |
P21280
|
FINISHED |
| Object | 0814-10-05 |
—
|
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: 0814-10-05 | Statement: [Louis I, coronationAsEmperor, 0814-10-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationAsEmperor Context triple: [Louis I, coronationAsEmperor, 0814-10-05]
-
A.
coronationAsCoEmperorDate
Indicates the date on which an individual was formally crowned or installed as a co-emperor alongside another reigning emperor.
-
B.
coronationAsKingOfTheRomans
Indicates the event in which a person is formally crowned and recognized as King of the Romans.
-
C.
crownedAs
Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
-
D.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
E.
wasCrowned
chosen
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
- 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.