Triple
T2047900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto I, Holy Roman Emperor |
E45495
|
entity |
| Predicate | coronationDateAsKingOfEastFrancia |
P35552
|
FINISHED |
| Object | 7 August 936 |
—
|
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: 7 August 936 | Statement: [Otto I, Holy Roman Emperor, coronationDateAsKingOfEastFrancia, 7 August 936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationDateAsKingOfEastFrancia Context triple: [Otto I, Holy Roman Emperor, coronationDateAsKingOfEastFrancia, 7 August 936]
-
A.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
B.
coronationPlaceAsHolyRomanEmperor
Indicates the place where a person was ceremonially crowned as Holy Roman Emperor.
-
C.
reignAsHolyRomanEmperorStart
Indicates the time point or event at which an entity begins its tenure as Holy Roman Emperor.
-
D.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
E.
coronationPlaceAsKingOfBohemia
Indicates the place where an individual was ceremonially crowned as King of Bohemia.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb974e8488190887b840c2cb88b3a |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:39 p.m.