Triple
T19869369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apasmara |
E477471
|
entity |
| Predicate | typicalPoseInArt |
P118773
|
FINISHED |
| Object | lying under the foot of Shiva |
—
|
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: lying under the foot of Shiva | Statement: [Apasmara, typicalPoseInArt, lying under the foot of Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPoseInArt Context triple: [Apasmara, typicalPoseInArt, lying under the foot of Shiva]
-
A.
showsPose
Indicates that one entity displays or presents a particular pose or bodily posture of another entity.
-
B.
artisticDepiction
Indicates that one entity visually represents, portrays, or illustrates another in an artistic medium.
-
C.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
-
D.
positionDepicted
chosen
Indicates that one entity visually represents or depicts the spatial position or placement of another entity.
-
E.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a2cc8481908d134b0b5cf79d06 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.