Triple
T20876849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell of Glenorchy |
E514037
|
entity |
| Predicate | usesClanBadge |
P117273
|
FINISHED |
| Object | Clan Campbell symbols |
—
|
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: Clan Campbell symbols | Statement: [Campbell of Glenorchy, usesClanBadge, Clan Campbell symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClanBadge Context triple: [Campbell of Glenorchy, usesClanBadge, Clan Campbell symbols]
-
A.
hasClanSymbol
chosen
Indicates that an entity is associated with a particular clan through a specific identifying symbol.
-
B.
hasClanBadgePlant
Indicates that an entity’s clan badge features or includes a specific plant as part of its design.
-
C.
sharesClanBadgeWith
Indicates that two entities possess and display the same clan badge, signifying shared clan affiliation or membership.
-
D.
usesClanPraise
Indicates that one entity employs or invokes the traditional praise names or laudatory expressions associated with a particular clan in relation to another entity.
-
E.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c6767ec0819080721e2e75bd0d66 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.