Triple
T22631467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Harishchandra |
E558564
|
entity |
| Predicate | receivesBoon |
P149000
|
FINISHED |
| Object | restoration of kingdom |
—
|
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: restoration of kingdom | Statement: [King Harishchandra, receivesBoon, restoration of kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesBoon Context triple: [King Harishchandra, receivesBoon, restoration of kingdom]
-
A.
obtainedBoonsFrom
Indicates that one entity has received or gained benefits, favors, or blessings from another entity.
-
B.
usedBoonsFrom
Indicates that one entity has utilized or expended beneficial effects, powers, or advantages that originated from another entity.
-
C.
awardedForToReceive
Indicates that an entity is granted an award or recognition in order to receive it for a specific reason, achievement, or qualifying basis.
-
D.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
E.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17009ecb0819082f94505b0e2c5b8 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:02 p.m.