Triple
T32627299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guhyasamāja |
E834092
|
entity |
| Predicate | mandalaType |
P51799
|
FINISHED |
| Object | thirty-two deity mandala |
—
|
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: thirty-two deity mandala | Statement: [Guhyasamāja, mandalaType, thirty-two deity mandala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandalaType Context triple: [Guhyasamāja, mandalaType, thirty-two deity mandala]
-
A.
mandala
chosen
Indicates a relationship in which something is depicted, structured, or functions as a mandala, typically embodying a symbolic, often circular, arrangement used for spiritual or meditative purposes.
-
B.
numberOfMandalas
Indicates the quantity or count of mandalas associated with a given entity.
-
C.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
-
D.
typicalMudra
Indicates that one entity is the characteristic or commonly used mudra (hand gesture) associated with another entity, such as a deity, practice, or tradition.
-
E.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.