Triple
T17302196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno Sospita |
E420064
|
entity |
| Predicate | iconographicallyDepictedWith |
P8270
|
FINISHED |
| Object | 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: shield | Statement: [Juno Sospita, iconographicallyDepictedWith, shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconographicallyDepictedWith Context triple: [Juno Sospita, iconographicallyDepictedWith, shield]
-
A.
iconographyFeature
chosen
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
B.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
-
C.
hasIconographicFigure
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
-
D.
iconographicForm
Indicates the specific visual or symbolic representation that an entity takes within an image or artwork.
-
E.
iconographicVariantOf
Indicates that one representation is an alternative visual or stylistic depiction of the same subject as another representation.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fba938819084333764b868bd83 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.