Triple
T22616609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish royal family |
E558163
|
entity |
| Predicate | dynasticNameChange |
P19579
|
FINISHED |
| Object | Stewart to Stuart |
—
|
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: Stewart to Stuart | Statement: [Scottish royal family, dynasticNameChange, Stewart to Stuart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticNameChange Context triple: [Scottish royal family, dynasticNameChange, Stewart to Stuart]
-
A.
dynasticNameChangedTo
chosen
Indicates that an entity’s dynastic name was replaced by or transitioned into a new dynastic name.
-
B.
dynasticSuccessionChangedBy
Indicates that a change or disruption has occurred in the established line of dynastic succession due to the influence or action of the related entity.
-
C.
dynastyChange
Indicates a transition in ruling power from one dynasty to another.
-
D.
dynastyBecameReigningHouseIn
Indicates that a particular dynasty became the officially ruling or dominant house of authority in a specified political entity or territory at a certain time.
-
E.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167eeb220819082c90a8bd3cadc4c |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:59 p.m.