Triple
T4685302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiranyakashipu |
E103906
|
entity |
| Predicate | boonDetails |
P59011
|
FINISHED |
| Object | could not be killed by man or beast |
—
|
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: could not be killed by man or beast | Statement: [Hiranyakashipu, boonDetails, could not be killed by man or beast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boonDetails Context triple: [Hiranyakashipu, boonDetails, could not be killed by man or beast]
-
A.
boosterType
Indicates the specific kind or category of booster associated with an entity 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.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
E.
featuresItem
Indicates that one entity includes, presents, or highlights another entity as a notable item or component.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:16 p.m.