Triple
T17956367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madri |
E448959
|
entity |
| Predicate | causeOfChildren |
P694
|
FINISHED |
| Object | boon of Kunti shared with her |
—
|
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: boon of Kunti shared with her | Statement: [Madri, causeOfChildren, boon of Kunti shared with her]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfChildren Context triple: [Madri, causeOfChildren, boon of Kunti shared with her]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeOfDaughterDeaths
Indicates a relationship where an entity is the cause or reason for the deaths of one or more daughters.
-
C.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
D.
causeStatedByPerpetrators
Indicates that the stated cause or reason for an event or action is the one explicitly given by the perpetrators themselves.
-
E.
parentalIssue
Indicates that there is a problem, conflict, or difficulty involving a person's relationship or situation with their parent(s).
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afafe814819085300163f73de5f2 |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.