Triple
T5491765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell of Argyll arms |
E123718
|
entity |
| Predicate | secondaryTincture |
P4605
|
FINISHED |
| Object | sable |
—
|
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: sable | Statement: [Campbell of Argyll arms, secondaryTincture, sable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTincture Context triple: [Campbell of Argyll arms, secondaryTincture, sable]
-
A.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryConstituent
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of another entity.
-
D.
secondaryPigment
chosen
Indicates that one pigment functions as a secondary or supporting color relative to another primary pigment in a given context.
-
E.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9280403c8190baaa3f7923449a37 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.