Triple
T24510306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Duchy of Cleves |
E606196
|
entity |
| Predicate | hasHeraldicOrdinary |
P156558
|
FINISHED |
| Object | chevron |
—
|
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: chevron | Statement: [Arms of the Duchy of Cleves, hasHeraldicOrdinary, chevron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeraldicOrdinary Context triple: [Arms of the Duchy of Cleves, hasHeraldicOrdinary, chevron]
-
A.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
B.
hasHeraldicMeaning
Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
-
C.
usesHeraldicStyle
Indicates that one entity employs or follows the heraldic style, conventions, or visual language associated with another entity.
-
D.
hasHeraldicBasis
Indicates that something is founded on, derived from, or justified by heraldic principles, symbols, or traditions.
-
E.
hasHeraldicSubject
Indicates that one entity serves as the heraldic subject or emblematic figure depicted on another entity, such as on a coat of arms or shield.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:23 a.m.