Triple
T24973785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Bishopric of Ely |
E624961
|
entity |
| Predicate | hasHeraldicMetal |
P100889
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Arms of the Bishopric of Ely, hasHeraldicMetal, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeraldicMetal Context triple: [Arms of the Bishopric of Ely, hasHeraldicMetal, gold]
-
A.
coatOfArmsMetal
chosen
Indicates that a coat of arms features a specific metal (such as gold or silver) as one of its heraldic tinctures.
-
B.
hasHeraldicOrdinary
Indicates that an entity bears or includes a specific heraldic ordinary (a basic geometric figure) as part of its coat of arms or heraldic design.
-
C.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
D.
hasHeraldicMeaning
Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
-
E.
hasHeraldicShieldShape
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 6:01 a.m.