Triple
T19026192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaka-vadha sub-parva |
E465615
|
entity |
| Predicate | featuresDeityOrPower |
P102272
|
FINISHED |
| Object | Bhima’s strength granted by Vayu |
—
|
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: Bhima’s strength granted by Vayu | Statement: [Vaka-vadha sub-parva, featuresDeityOrPower, Bhima’s strength granted by Vayu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDeityOrPower Context triple: [Vaka-vadha sub-parva, featuresDeityOrPower, Bhima’s strength granted by Vayu]
-
A.
featuresDeity
Indicates that a work, object, or context prominently includes, depicts, or centers around a particular deity.
-
B.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
C.
associatedDeityOrForce
chosen
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
D.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
E.
featuresPowerUp
Indicates that one entity includes, provides, or incorporates a power-up as part of its content or functionality.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d73cace0819096bdac6dc8c17253 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.