Triple
T25589095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vindhyavasini |
E641469
|
entity |
| Predicate | powerAspect |
P118971
|
FINISHED |
| Object | Mahashakti of Vindhya region |
—
|
NE NERFINISHED |
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: Mahashakti of Vindhya region | Statement: [Vindhyavasini, powerAspect, Mahashakti of Vindhya region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerAspect Context triple: [Vindhyavasini, powerAspect, Mahashakti of Vindhya region]
-
A.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
B.
powersType
chosen
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
C.
powerPosition
Indicates that one entity holds a position of authority, control, or dominance over another within a hierarchy or power structure.
-
D.
powerScope
Indicates the extent or domain within which an entity’s power, authority, or influence is valid or can be exercised.
-
E.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96bfb00819090b954159c413b28 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:18 p.m.