Triple
T966735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimamsa |
E20853
|
entity |
| Predicate | placesAboveOtherPramanas |
P22242
|
FINISHED |
| Object | Vedic verbal testimony |
—
|
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: Vedic verbal testimony | Statement: [Mimamsa, placesAboveOtherPramanas, Vedic verbal testimony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesAboveOtherPramanas Context triple: [Mimamsa, placesAboveOtherPramanas, Vedic verbal testimony]
-
A.
positionOnMetaphysics
Indicates a relationship where an entity’s stance, view, or theoretical commitment regarding metaphysical questions or issues is specified.
-
B.
positionInKantsSystem
Indicates the specific role or place that something occupies within Immanuel Kant’s overall philosophical system.
-
C.
equivalentInBuddhism
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
-
D.
viewOnOtherDeities
Indicates how one deity regards, evaluates, or conceptually relates to other deities.
-
E.
philosophicalMethod
Indicates the method, approach, or technique used in conducting philosophical inquiry or reasoning.
- F. None of above. chosen
Provenance (4 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43412488190b68e33d2b36a0ba3 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.