Triple
T25571470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torquhil Ian Campbell |
E640983
|
entity |
| Predicate | clanChiefRank |
P158655
|
FINISHED |
| Object | chief of Clan Campbell |
—
|
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: chief of Clan Campbell | Statement: [Torquhil Ian Campbell, clanChiefRank, chief of Clan Campbell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanChiefRank Context triple: [Torquhil Ian Campbell, clanChiefRank, chief of Clan Campbell]
-
A.
clanChiefRecognition
Indicates that an individual is formally acknowledged or endorsed as a chief by a particular clan or its traditional authority.
-
B.
clanChiefTitleOf
Indicates that one entity is the formal title held by the chief or leader of a particular clan.
-
C.
clanChiefBranchOf
Indicates that a particular clan chief belongs to, or is a leading figure within, a specific branch or subdivision of a larger clan.
-
D.
traditionalClanChief
Indicates that one entity serves as the recognized traditional clan chief or customary leader of another entity (typically a clan or community).
-
E.
parentClanChief
Indicates that one entity serves as the clan chief of the parent clan of another entity.
- F. None of above. chosen
Provenance (4 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f92cf9ec8190ab84aac07b4c2886 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 3:58 p.m.