Triple
T3259595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Emmanuel III of Sardinia |
E68376
|
entity |
| Predicate | succeededToThrone |
P46927
|
FINISHED |
| Object | Kingdom of Sardinia in 1730 |
—
|
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: Kingdom of Sardinia in 1730 | Statement: [Charles Emmanuel III of Sardinia, succeededToThrone, Kingdom of Sardinia in 1730]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededToThrone Context triple: [Charles Emmanuel III of Sardinia, succeededToThrone, Kingdom of Sardinia in 1730]
-
A.
succeededToThroneAs
Indicates that one entity became the new ruler by taking over the throne in a specified role or title from another entity.
-
B.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
-
C.
crownedAs
Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
-
D.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
E.
monarchSuccessor
Indicates that one monarch directly follows another in a royal line of succession.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adafa4f40c81909adfd0f7f568e3ce |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.