Triple
T22187202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Kinship |
E548324
|
entity |
| Predicate | iconographicStructure |
P146755
|
FINISHED |
| Object | multi-generational family group |
—
|
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: multi-generational family group | Statement: [Holy Kinship, iconographicStructure, multi-generational family group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconographicStructure Context triple: [Holy Kinship, iconographicStructure, multi-generational family group]
-
A.
iconographicForm
Indicates the specific visual or symbolic representation that an entity takes within an image or artwork.
-
B.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
C.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
-
D.
iconographicFunction
Indicates the symbolic or representational role that something serves within an image or visual composition.
-
E.
iconographicSubject
Indicates that one entity serves as the depicted subject or theme represented in the iconography 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aaa32288190830f6dfc626fb26a |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.