Triple
T24787668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Alcoraz |
E620161
|
entity |
| Predicate | heraldicTinctureCross |
P74089
|
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: [Cross of Alcoraz, heraldicTinctureCross, gules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heraldicTinctureCross Context triple: [Cross of Alcoraz, heraldicTinctureCross, gules]
-
A.
heraldicTinctureRed
chosen
Indicates that an entity in a heraldic context is colored or depicted with the red tincture (gules).
-
B.
crossTincture
Indicates that one entity bears or displays a cross whose tincture (heraldic color or pattern) is specified or characterized in relation to another entity.
-
C.
fieldForCrossTincture
Indicates that a field (background area) is designated to receive a cross tincture (coloring or pattern) in a heraldic design.
-
D.
heraldicCharge
Indicates that one entity serves as a heraldic charge, i.e., a symbolic figure or emblem placed on another entity’s coat of arms or shield.
-
E.
heraldicColor
Indicates that one entity specifies or bears a particular heraldic color in a coat of arms or related heraldic context.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110071008190a430ca780b567fe4 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:46 a.m.