Triple
T1553749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Dunkeld |
E33152
|
entity |
| Predicate | successorStateDevelopment |
P3025
|
FINISHED |
| Object | centralised Scottish kingdom |
—
|
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: centralised Scottish kingdom | Statement: [House of Dunkeld, successorStateDevelopment, centralised Scottish kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorStateDevelopment Context triple: [House of Dunkeld, successorStateDevelopment, centralised Scottish kingdom]
-
A.
successorState
chosen
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
B.
successorStateRole
Indicates that one role represents the state or position that directly follows and replaces another role in a sequence or process.
-
C.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorProcess
Indicates that one process directly follows another in a defined sequence or workflow.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.