Triple
T923574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiva |
E19933
|
entity |
| Predicate | iconographicFeature |
P8270
|
FINISHED |
| Object | blue throat |
—
|
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: blue throat | Statement: [Shiva, iconographicFeature, blue throat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconographicFeature Context triple: [Shiva, iconographicFeature, blue throat]
-
A.
iconographyFeature
chosen
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
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.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
D.
artisticCharacteristic
Indicates that one entity possesses or exhibits a particular artistic quality, style, or trait in relation to another.
-
E.
hasIconostasis
Indicates that a place of worship contains or is equipped with an iconostasis, a partition or screen bearing icons that separates different liturgical spaces.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3296f50819087f809fbe90b139e |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.