Triple
T15289687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columba |
E365493
|
entity |
| Predicate | hasIconographyAttribute |
P37076
|
FINISHED |
| Object | dove |
—
|
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: dove | Statement: [Columba, hasIconographyAttribute, dove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconographyAttribute Context triple: [Columba, hasIconographyAttribute, dove]
-
A.
hasIconographicFigure
chosen
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
-
B.
hasIconographicTradition
Indicates that an entity is associated with a recognized, recurring set of visual motifs or symbolic representations within a particular artistic or cultural tradition.
-
C.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
-
D.
iconographyStatus
Indicates the current condition, completeness, or interpretive state of an entity’s iconographic representation.
-
E.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e5635b4819092a69b5806d15bff |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.