Triple
T14418617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerr family |
E357520
|
entity |
| Predicate | hereditaryRole |
P6021
|
FINISHED |
| Object | Scottish peers |
—
|
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: Scottish peers | Statement: [Kerr family, hereditaryRole, Scottish peers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryRole Context triple: [Kerr family, hereditaryRole, Scottish peers]
-
A.
successionRole
Indicates a role or position that one entity assumes as the successor to another in a sequence of holders or office-bearers.
-
B.
successorRole
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
C.
hasHereditaryOffice
chosen
Indicates that an entity holds an office or position that is passed down through family lineage rather than acquired by election, appointment, or merit.
-
D.
heritageSuccessor
Indicates that one entity is the successor or inheritor of another in terms of heritage, lineage, or cultural tradition.
-
E.
hasRoleInSuccession
Indicates that an entity holds a specific role or position within a defined line or order of succession.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.