Triple
T10420648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of the Grand Duchy of Tuscany |
E245637
|
entity |
| Predicate | symbolFeature |
P64220
|
FINISHED |
| Object | red balls (palle) on a gold shield |
—
|
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: red balls (palle) on a gold shield | Statement: [coat of arms of the Grand Duchy of Tuscany, symbolFeature, red balls (palle) on a gold shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolFeature Context triple: [coat of arms of the Grand Duchy of Tuscany, symbolFeature, red balls (palle) on a gold shield]
-
A.
symbolVariant
Indicates that one symbol is an alternative graphical or stylistic form of another symbol.
-
B.
namedFeature
chosen
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
C.
metricalFeature
Indicates a relationship where one entity specifies or characterizes a metrical property or pattern of another entity.
-
D.
symbolDesigned
Indicates that one entity created or planned the design of a symbolic representation (such as a logo, icon, or emblem) for another entity.
-
E.
symbolText
Indicates that a symbol is associated with or represented by a specific piece of text.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2bee2081908e5e65df9100d463 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:11 p.m.