Triple
T9516906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croce di Guerra al Valor Militare |
E229547
|
entity |
| Predicate | decorativeForm |
P60999
|
FINISHED |
| Object | breast decoration |
—
|
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: breast decoration | Statement: [Croce di Guerra al Valor Militare, decorativeForm, breast decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorativeForm Context triple: [Croce di Guerra al Valor Militare, decorativeForm, breast decoration]
-
A.
decorationForm
chosen
Indicates the specific decorative style, pattern, or motif that characterizes how something is ornamented.
-
B.
decorationShape
Indicates the geometric or visual form that a decorative element or ornament takes in relation to the object it adorns.
-
C.
decorativeCategory
Indicates that one entity is classified as belonging to a particular decorative style, theme, or ornamentation category of another entity.
-
D.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied to another entity.
-
E.
decorativeComplexity
Indicates the degree or richness of ornamental detail or embellishment present in something.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd987eefec8190b0db1928776bf02b |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.