Triple
T19698722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhishma |
E473034
|
entity |
| Predicate | blessedWith |
P136973
|
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, blessedWith, iccha-mrityu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blessedWith Context triple: [Bhishma, blessedWith, iccha-mrityu]
-
A.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
B.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
C.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
-
D.
firstBlessing
Indicates that an entity is the initial recipient or instance of a blessing in relation to another entity or context.
-
E.
blessingRecordedIn
Indicates that a blessing event or act has been documented or preserved within a specific record, text, or medium.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b426608190a46abec3652a6ca0 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.