Triple
T21319416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parikshit |
E525570
|
entity |
| Predicate | cursedToDieIn |
P143703
|
FINISHED |
| Object | seven days |
—
|
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: seven days | Statement: [Parikshit, cursedToDieIn, seven days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cursedToDieIn Context triple: [Parikshit, cursedToDieIn, seven days]
-
A.
diesInArmsOf
Indicates that one entity dies while being physically held or embraced by another entity.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
cannotDieInHumanSense
Indicates that the entity is not subject to death or mortality in the way humans experience or understand it.
-
D.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
-
E.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ecf12248190bb4172ad7416775e |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:38 p.m.