Triple
T859484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyaya |
E18567
|
entity |
| Predicate | recognizesPramana |
P310
|
FINISHED |
| Object | perception (pratyaksha) |
—
|
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 (pratyaksha) | Statement: [Nyaya, recognizesPramana, perception (pratyaksha)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesPramana Context triple: [Nyaya, recognizesPramana, perception (pratyaksha)]
-
A.
recognizesPillar
Indicates that one entity acknowledges or identifies another entity as a fundamental support, key element, or core principle within a given context.
-
B.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
C.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
D.
canRecognize
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
-
E.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.