Triple
T304554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles I of Spain |
E6268
|
entity |
| Predicate | reignEndAsHolyRomanEmperor |
P2721
|
FINISHED |
| Object | 1556 |
—
|
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: 1556 | Statement: [Charles I of Spain, reignEndAsHolyRomanEmperor, 1556]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndAsHolyRomanEmperor Context triple: [Charles I of Spain, reignEndAsHolyRomanEmperor, 1556]
-
A.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
abdicatedInFavorOf
Indicates that one entity has voluntarily renounced a position, role, or right so that another specific entity may assume it.
-
C.
previousEmperorReignName
Indicates that the subject emperor’s reign name immediately precedes the object emperor’s reign name in historical succession.
-
D.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
E.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea1032e48190864338e030d9dc92 |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.