Triple
T21502773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie, Duchess of Hohenberg |
E530519
|
entity |
| Predicate | elevatedToDuchess |
P144638
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Sophie, Duchess of Hohenberg, elevatedToDuchess, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToDuchess Context triple: [Sophie, Duchess of Hohenberg, elevatedToDuchess, 1909]
-
A.
elevatedToDuchy
Indicates that a territory, region, or domain has been formally raised in rank or status to become a duchy.
-
B.
reignAsDuchessFrom
Indicates that a person holds and exercises the title and authority of a duchess over a specified domain starting from a given point in time.
-
C.
reignAsDuchessTo
Indicates that one entity holds and exercises the title and authority of duchess in relation to another specified domain, territory, or noble house.
-
D.
elevatedToArchduchy
Indicates that an entity’s status or rank has been raised to that of an archduchy.
-
E.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5d209881908754eb07a47e478a |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:24 p.m.