Triple
T30776450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Bhagiratha |
E783685
|
entity |
| Predicate | performedPenanceTo |
P194314
|
FINISHED |
| Object | Lord Brahma |
—
|
NE NERFINISHED |
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: Lord Brahma | Statement: [King Bhagiratha, performedPenanceTo, Lord Brahma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedPenanceTo Context triple: [King Bhagiratha, performedPenanceTo, Lord Brahma]
-
A.
performedPenanceAt
Indicates that an entity carried out an act of penance at a specific place or location.
-
B.
penance
Indicates an act of self-imposed suffering, discipline, or reparation performed to atone for a wrongdoing or moral failing.
-
C.
goalOfPenance
Indicates that an action or practice is performed with the specific purpose of making amends, seeking forgiveness, or achieving spiritual or moral purification.
-
D.
repentedTo
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
-
E.
demandedAtonementFrom
Indicates that one entity required another to make amends or provide compensation for a perceived wrong or offense.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
| PDg | Predicate description generation | batch_69fd6a1a38f081908c573aee4696de4f |
completed | May 8, 2026, 4:44 a.m. |
Created at: April 29, 2026, 8:40 p.m.