Triple
T31645237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabhi |
E807567
|
entity |
| Predicate | vakraPrayoga |
P172049
|
FINISHED |
| Object | present |
—
|
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: present | Statement: [Arabhi, vakraPrayoga, present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vakraPrayoga Context triple: [Arabhi, vakraPrayoga, present]
-
A.
vakul
Indicates a relationship or action between entities, but the specific meaning of the predicate "vakul" is unclear without additional context or definition.
-
B.
vadi
Indicates that one entity is speaking, arguing, or verbally expressing something to another entity.
-
C.
vise
Indicates that one entity firmly grips, clamps, or holds another in place, typically restricting its movement or separating it from other objects.
-
D.
via
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
E.
vitDans
Indicates that one entity lives or resides in the location represented by another 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:50 p.m.