Triple
T2108902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Moscow |
E42457
|
entity |
| Predicate | iconographyType |
P34813
|
FINISHED |
| Object | Christian iconography |
—
|
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: Christian iconography | Statement: [flag of Moscow, iconographyType, Christian iconography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconographyType Context triple: [flag of Moscow, iconographyType, Christian iconography]
-
A.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
B.
iconographicFunction
Indicates the symbolic or representational role that something serves within an image or visual composition.
-
C.
iconographicVariant
Indicates that one representation is an alternative or variant visual depiction of another within an iconographic tradition or system.
-
D.
iconographicVariantOf
Indicates that one representation is an alternative visual or stylistic depiction of the same subject as another representation.
-
E.
iconOf
Indicates that one entity serves as a symbolic or representative image or emblem of another entity.
- F. None of above. chosen
Provenance (4 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae03f308190841f5a419bb821f6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:43 p.m.