Triple
T33039875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cakrasaṃvara |
E845430
|
entity |
| Predicate | primaryConsort |
P206330
|
FINISHED |
| Object | Vajravārāhī |
E1342525
|
NE 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: Vajravārāhī | Statement: [Cakrasaṃvara, primaryConsort, Vajravārāhī]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConsort Context triple: [Cakrasaṃvara, primaryConsort, Vajravārāhī]
-
A.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
B.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
C.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
D.
primarySeries
Indicates that one entity is the main or principal sequence, set, or collection to which another entity is related or belongs.
-
E.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept or context.
- F. None of above. chosen
Provenance (5 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e514028881909b035453ccb154cd |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:24 a.m.