Triple
T4512968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uddyotakara |
E102091
|
entity |
| Predicate | acceptedPramana |
P57100
|
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: [Uddyotakara, acceptedPramana, perception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedPramana Context triple: [Uddyotakara, acceptedPramana, perception]
-
A.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
B.
approvedPractice
Indicates that a particular practice, method, or procedure has been formally reviewed and granted official approval for use or adoption.
-
C.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
D.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
E.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.