Triple
T19963387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paramapada |
E479870
|
entity |
| Predicate | attainableThrough |
P16015
|
FINISHED |
| Object | bhakti |
—
|
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: bhakti | Statement: [Paramapada, attainableThrough, bhakti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attainableThrough Context triple: [Paramapada, attainableThrough, bhakti]
-
A.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of another entity.
-
D.
canAchieve
chosen
Indicates that an entity has the ability or potential to successfully attain or accomplish a specified goal, state, or outcome.
-
E.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af619108190825cbcfb6b8e1fa5 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.