Triple
T22802180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Meurthe-et-Moselle |
E564425
|
entity |
| Predicate | usesHeraldicTincture |
P95589
|
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: [coat of arms of Meurthe-et-Moselle, usesHeraldicTincture, gules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeraldicTincture Context triple: [coat of arms of Meurthe-et-Moselle, usesHeraldicTincture, gules]
-
A.
heraldicTinctureRed
Indicates that an entity in a heraldic context is colored or depicted with the red tincture (gules).
-
B.
heraldicColor
chosen
Indicates that one entity specifies or bears a particular heraldic color in a coat of arms or related heraldic context.
-
C.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
D.
usesHeraldicStyle
Indicates that one entity employs or follows the heraldic style, conventions, or visual language associated with another entity.
-
E.
hasHeraldicMeaning
Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdf1e308190a05d0f61856be544 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.