Triple
T21259876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of Clan Campbell |
E523968
|
entity |
| Predicate | nobleRankAssociation |
P66828
|
FINISHED |
| Object | peerage of Scotland |
—
|
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: peerage of Scotland | Statement: [Chief of Clan Campbell, nobleRankAssociation, peerage of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankAssociation Context triple: [Chief of Clan Campbell, nobleRankAssociation, peerage of Scotland]
-
A.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
B.
nobleRankIn
chosen
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
C.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
D.
nobleRankInOrder
Indicates that an entity holds a specific noble rank at a particular position within an established order of nobility.
-
E.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e53df88190bd6024793a0ada08 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.