Triple
T35968538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Bohemia |
E1040211
|
entity |
| Predicate | successorTitleInEmpire |
P201984
|
FINISHED |
| Object | Archduchess of Austria |
—
|
NE NERFINISHED |
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: Archduchess of Austria | Statement: [Princess of Bohemia, successorTitleInEmpire, Archduchess of Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitleInEmpire Context triple: [Princess of Bohemia, successorTitleInEmpire, Archduchess of Austria]
-
A.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
B.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
-
C.
successorThroneNameOfBearer
Indicates that the object is the throne name adopted by the successor of the subject bearer.
-
D.
successorSovereign
Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
-
E.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
| PDg | Predicate description generation | batch_6a003ffa64e48190b37cce7d1c939b78 |
completed | May 10, 2026, 8:21 a.m. |
Created at: May 3, 2026, 4:07 p.m.