Triple
T33039904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cakrasaṃvara |
E845430
|
entity |
| Predicate | hasMandalas |
P51799
|
FINISHED |
| Object | five-deity Cakrasaṃvara maṇḍala |
—
|
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: five-deity Cakrasaṃvara maṇḍala | Statement: [Cakrasaṃvara, hasMandalas, five-deity Cakrasaṃvara maṇḍala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMandalas Context triple: [Cakrasaṃvara, hasMandalas, five-deity Cakrasaṃvara maṇḍala]
-
A.
numberOfMandalas
Indicates the quantity or count of mandalas associated with a given entity.
-
B.
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.
-
C.
hasMandalStatus
Indicates that an entity holds or is assigned a specific mandal-level administrative or organizational status.
-
D.
hasMosaic
Indicates that one entity possesses, contains, or is decorated with a mosaic.
-
E.
hasMosaicsBy
Indicates that something contains or features mosaics that were created by a specified agent or creator.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:24 a.m.