Triple
T12144859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto IV, Holy Roman Emperor |
E289290
|
entity |
| Predicate | imperialReignEnd |
P35129
|
FINISHED |
| Object | 1215 |
—
|
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: 1215 | Statement: [Otto IV, Holy Roman Emperor, imperialReignEnd, 1215]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialReignEnd Context triple: [Otto IV, Holy Roman Emperor, imperialReignEnd, 1215]
-
A.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
B.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
endEmperor
chosen
Indicates the point or event at which an individual's tenure or status as emperor comes to an end.
-
D.
thirdHolderReignEnd
Indicates the date or point in time when the reign or tenure of the third holder of a title, office, or position comes to an end.
-
E.
coEmperorEnd
Indicates that one entity’s tenure as co-emperor with another entity comes to an end at a specific point in time.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.