Triple
T109424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peerage of Scotland |
E2211
|
entity |
| Predicate | hasSuccessionRule |
P545
|
FINISHED |
| Object | canIncludeHeirs-general in some titles |
—
|
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: canIncludeHeirs-general in some titles | Statement: [Peerage of Scotland, hasSuccessionRule, canIncludeHeirs-general in some titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessionRule Context triple: [Peerage of Scotland, hasSuccessionRule, canIncludeHeirs-general in some titles]
-
A.
successionDefinedBy
chosen
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
-
B.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
C.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
D.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
E.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563fd2fc819090265edbfe3092d6 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.