Triple
T4817139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhishma |
E107614
|
entity |
| Predicate | boon |
P59011
|
FINISHED |
| Object | iccha-mrityu |
—
|
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: iccha-mrityu | Statement: [Bhishma, boon, iccha-mrityu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boon Context triple: [Bhishma, boon, iccha-mrityu]
-
A.
boonDetails
chosen
Indicates the specific terms, conditions, or characteristics associated with a granted benefit or favor within the relationship or action.
-
B.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
-
C.
bounty
Indicates that a reward or payment is offered for performing a specific action or achieving a particular outcome related to an entity.
-
D.
beyond
Indicates that one entity is located or extends farther than, or outside the limits or scope of, another reference point or boundary.
-
E.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.