Triple
T23980537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernadotte dynasty |
E604494
|
entity |
| Predicate | founderBecameHeirTo |
P154113
|
FINISHED |
| Object | Swedish throne |
—
|
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: Swedish throne | Statement: [Bernadotte dynasty, founderBecameHeirTo, Swedish throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderBecameHeirTo Context triple: [Bernadotte dynasty, founderBecameHeirTo, Swedish throne]
-
A.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
B.
succeededToThroneBy
Indicates that one ruler or monarch is followed in succession by another who takes over the throne.
-
C.
succeededOnThroneAfter
Indicates that one entity became the ruler or monarch immediately following another entity’s reign on the same throne.
-
D.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
E.
successorAsLordOf
Indicates that one entity takes over the role or title of lord from another entity, becoming their direct successor in that lordship.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bd58448190a64e7a9020109229 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:27 p.m.