Triple
T5117662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugriva |
E115376
|
entity |
| Predicate | receivesPromiseFrom |
P4382
|
FINISHED |
| Object | Rama to kill Vali |
—
|
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: Rama to kill Vali | Statement: [Sugriva, receivesPromiseFrom, Rama to kill Vali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesPromiseFrom Context triple: [Sugriva, receivesPromiseFrom, Rama to kill Vali]
-
A.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
-
B.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
C.
corePromise
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
-
D.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
E.
childOfPromiseThrough
Indicates a relationship where an entity is considered a child or descendant specifically by virtue of a promise or covenant, rather than by ordinary lineage or means.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:41 p.m.