Triple
T2283004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kriophoros |
E51321
|
entity |
| Predicate | hasIconographicElement |
P8270
|
FINISHED |
| Object | ram |
—
|
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: ram | Statement: [Kriophoros, hasIconographicElement, ram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconographicElement Context triple: [Kriophoros, hasIconographicElement, ram]
-
A.
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.
-
B.
iconographyFeature
chosen
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
C.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
-
D.
hasIconicArtifact
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
-
E.
hasIconicStructure
Indicates that an entity possesses a structure or feature that is widely recognized as emblematic or symbolically representative of it.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21d6d748190980128c1bc5b9621 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.