Triple
T11624716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto III, Holy Roman Emperor |
E276234
|
entity |
| Predicate | reignAsKingOfGermany |
P36565
|
FINISHED |
| Object | 983-1002 |
—
|
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: 983-1002 | Statement: [Otto III, Holy Roman Emperor, reignAsKingOfGermany, 983-1002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsKingOfGermany Context triple: [Otto III, Holy Roman Emperor, reignAsKingOfGermany, 983-1002]
-
A.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
-
B.
reignAsKingOfGermanyStart
chosen
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
C.
reignStartAsGermanEmperor
Indicates the time at which an individual began their rule in the role of German Emperor.
-
D.
successorAsGermanEmperor
Indicates that one entity became the next holder of the title of German Emperor directly after another entity.
-
E.
reignAsDukeOfBavariaTo
Indicates that one entity holds and exercises the title and authority of Duke of Bavaria over another entity (typically a territory or domain).
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a12416908190ac2dcd7f7ebb308f |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.