Triple
T17951074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padmapada |
E448831
|
entity |
| Predicate | doctrineRejects |
P5486
|
FINISHED |
| Object | dualist interpretations of Vedanta |
—
|
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: dualist interpretations of Vedanta | Statement: [Padmapada, doctrineRejects, dualist interpretations of Vedanta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineRejects Context triple: [Padmapada, doctrineRejects, dualist interpretations of Vedanta]
-
A.
deniesDoctrine
chosen
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
-
B.
disapprovedOf
Indicates that one entity holds a negative judgment or lack of approval toward another entity or that entity’s actions.
-
C.
doctrineDiscussed
Indicates that a particular doctrine is the topic of discussion or analysis in a given context or interaction.
-
D.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
E.
doctrineChallenged
Indicates that a particular doctrine, principle, or set of beliefs is being questioned, disputed, or formally contested.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afac95048190a5d1ef012899c62b |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.