Triple
T26050211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Anna of Tyrol |
E647950
|
entity |
| Predicate | reignAsHolyRomanEmpress |
P73696
|
FINISHED |
| Object | 1612-1618 |
—
|
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: 1612-1618 | Statement: [Empress Anna of Tyrol, reignAsHolyRomanEmpress, 1612-1618]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsHolyRomanEmpress Context triple: [Empress Anna of Tyrol, reignAsHolyRomanEmpress, 1612-1618]
-
A.
successorAsHolyRomanEmpress
Indicates that one person assumed the role of Holy Roman Empress directly after another, succeeding her in that position.
-
B.
reignAsHolyRomanEmpressConsortEnd
chosen
Indicates the time or event at which an individual’s tenure as Holy Roman Empress consort comes to an end.
-
C.
reignAsEmpress
Indicates that a person holds and exercises the supreme imperial authority in the role of empress over a realm or empire.
-
D.
reignAsGermanEmpressStart
Indicates the point in time when an individual begins their tenure as German Empress.
-
E.
crownedHolyRomanEmperor
Indicates that a person has been formally invested with the title and authority of Holy Roman Emperor through a coronation ceremony.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 9:10 a.m.