Triple
T859495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyaya |
E18567
|
entity |
| Predicate | definesCategory |
P87
|
FINISHED |
| Object | substance (dravya) |
—
|
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: substance (dravya) | Statement: [Nyaya, definesCategory, substance (dravya)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCategory Context triple: [Nyaya, definesCategory, substance (dravya)]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
C.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
D.
scriptCategory
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
-
E.
associatedStationCategory
Indicates that one entity is linked to, or classified under, a particular category of station.
- 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.