Triple
T25693409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushti (divine grace) |
E644255
|
entity |
| Predicate | doctrineLocation |
P11295
|
FINISHED |
| Object | Vallabha’s Shuddhadvaita Vedanta |
—
|
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: Vallabha’s Shuddhadvaita Vedanta | Statement: [Pushti (divine grace), doctrineLocation, Vallabha’s Shuddhadvaita Vedanta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineLocation Context triple: [Pushti (divine grace), doctrineLocation, Vallabha’s Shuddhadvaita Vedanta]
-
A.
configurationLocation
Indicates the place or context where a configuration is stored, applied, or defined.
-
B.
documentationLocation
Indicates the place or resource where relevant documentation for an entity can be found.
-
C.
implementationLocation
Indicates the place or environment where something is implemented, carried out, or put into effect.
-
D.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
E.
doctrineSourceFor
chosen
Indicates that one entity serves as the originating basis or authoritative source of doctrine, teachings, or principles 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 8:31 p.m.