Triple
T19593913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishi Kanva |
E470302
|
entity |
| Predicate | typeOfRishi |
P136393
|
FINISHED |
| Object | Vedic rishi |
—
|
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 rishi | Statement: [Rishi Kanva, typeOfRishi, Vedic rishi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRishi Context triple: [Rishi Kanva, typeOfRishi, Vedic rishi]
-
A.
associatedRishi
Indicates a relationship where a given entity is linked or connected to a particular rishi (sage), typically as being attributed to, guided by, or traditionally related to that rishi.
-
B.
roleInRishiRichProject
Indicates that an entity holds or held a specific role or function within the Rishi Rich Project.
-
C.
typeOfMonk
Indicates that one entity is a specific kind or category of monk in relation to another entity.
-
D.
typeOfCharacter
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
E.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640782e2c8190b5baef07a2bdd015 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.