Triple
T31736717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drummond family arms |
E810018
|
entity |
| Predicate | tinctureOfBarsWavy |
P172899
|
FINISHED |
| Object | Gules |
—
|
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: Gules | Statement: [Drummond family arms, tinctureOfBarsWavy, Gules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureOfBarsWavy Context triple: [Drummond family arms, tinctureOfBarsWavy, Gules]
-
A.
tinctureWaves
Indicates that one entity imparts a coloring or tinting effect onto another in a manner likened to spreading or rippling waves.
-
B.
tinctureOfChevrons
Indicates that one entity bears or features a heraldic design consisting of multiple chevrons arranged together, typically in a specific tincture (color or metal).
-
C.
tinctureWhite
Indicates that an entity has the heraldic tincture (color) white or silver as a defining attribute or feature.
-
D.
tinctureRed
Indicates that an entity has a red-colored tincture (heraldic coloring) applied to it.
-
E.
tinctureOfBordure
Indicates that one element is depicted as a tincture (color or pattern) specifically applied to the bordure (border) of another element.
- F. None of above. chosen
Provenance (4 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:23 p.m.