Triple
T6872921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samkhyakarika |
E158595
|
entity |
| Predicate | usesEpistemicMeans |
P73855
|
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: [Samkhyakarika, usesEpistemicMeans, perception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEpistemicMeans Context triple: [Samkhyakarika, usesEpistemicMeans, perception]
-
A.
epistemicAttitude
Indicates the type or stance of a subject’s knowledge, belief, or certainty toward a proposition or statement.
-
B.
epistemicRole
Indicates the role an entity plays in a knowledge-related context, such as being a knower, source, or bearer of information or belief.
-
C.
epistemicStatus
Indicates the degree of certainty, justification, or knowledge an agent has regarding a particular proposition or claim.
-
D.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
E.
usesIntelligence
Indicates that an entity applies mental abilities such as reasoning, problem-solving, or understanding to perform an action or achieve a goal.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c73ea08190b6bb1463e7ead47b |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:22 p.m.