Triple
T5708166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of Gordon, Marquess of Huntly |
E125836
|
entity |
| Predicate | primaryChargeTincture |
P24010
|
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: [Arms of Gordon, Marquess of Huntly, primaryChargeTincture, sable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryChargeTincture Context triple: [Arms of Gordon, Marquess of Huntly, primaryChargeTincture, sable]
-
A.
chargeTincture
chosen
Indicates that a heraldic charge bears a specific tincture (color, metal, or fur) in a coat of arms.
-
B.
chiefTincture
Indicates that one entity serves as the primary or dominant coloring or tonal quality in relation to another entity.
-
C.
tongueTincture
Indicates that an entity applies or administers a tincture by placing it on or under the tongue.
-
D.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
E.
tinctureOrdinary
Indicates that an ordinary (a basic heraldic shape or charge) is depicted with a specific tincture (color, metal, or fur) in a coat of arms.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248ab6a88190be17bdc32c36e5cb |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.