Triple
T19594406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu philosophy |
E470313
|
entity |
| Predicate | usesPramana |
P1757
|
FINISHED |
| Object | perception |
—
|
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: perception | Statement: [Hindu philosophy, usesPramana, perception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPramana Context triple: [Hindu philosophy, usesPramana, perception]
-
A.
acceptedPramana
Indicates that one entity has acknowledged and accepted another entity as a valid source of knowledge or authority.
-
B.
numberOfPramanas
Indicates the relationship that specifies how many distinct means of valid knowledge (pramāṇas) are recognized or associated in a given epistemic system or context.
-
C.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
D.
usesPrinciple
chosen
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
E.
acceptsNumberOfPramanas
Indicates that an entity recognizes, allows, or adopts a specific number of valid means of knowledge (pramāṇas) within its epistemological framework.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640793cd88190b9b84491bfb2493f |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.