Triple
T25603894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Own Highlanders (Seaforth and Camerons) |
E641856
|
entity |
| Predicate | capBadgeMotto |
P111085
|
FINISHED |
| Object | Cuidich 'n Righ |
—
|
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: Cuidich 'n Righ | Statement: [Queen's Own Highlanders (Seaforth and Camerons), capBadgeMotto, Cuidich 'n Righ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capBadgeMotto Context triple: [Queen's Own Highlanders (Seaforth and Camerons), capBadgeMotto, Cuidich 'n Righ]
-
A.
mottoOrInsigniaTheme
Indicates that a motto or insignia is based on, refers to, or thematically centers around a particular concept, idea, or subject.
-
B.
hasMottoRibbon
Indicates that an entity features or is associated with a ribbon element specifically used to display a motto.
-
C.
mottoOrNickname
chosen
Indicates that one entity serves as a motto, slogan, or nickname associated with another entity.
-
D.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
E.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a89830819083b11f0b818e538d |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:37 p.m.