Triple
T21358003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Argyll |
E526687
|
entity |
| Predicate | clanChiefRole |
P23606
|
FINISHED |
| Object | hereditary 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: hereditary chief of Clan Campbell | Statement: [Marquess of Argyll, clanChiefRole, hereditary chief of Clan Campbell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanChiefRole Context triple: [Marquess of Argyll, clanChiefRole, hereditary chief of Clan Campbell]
-
A.
parentClanChief
Indicates that one entity serves as the clan chief of the parent clan of another entity.
-
B.
clanChiefRecognition
Indicates that an individual is formally acknowledged or endorsed as a chief by a particular clan or its traditional authority.
-
C.
clanChiefTitleOf
chosen
Indicates that one entity is the formal title held by the chief or leader of a particular clan.
-
D.
clanChiefBranchOf
Indicates that a particular clan chief belongs to, or is a leading figure within, a specific branch or subdivision of a larger clan.
-
E.
clanChiefStyle
Indicates the formal title or style used to address or refer to the chief of a clan.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8afa2d11c81908608851940e4e6d3 |
completed | April 22, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:07 p.m.