Triple
T20135819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suka |
E491021
|
entity |
| Predicate | narrationPurpose |
P80898
|
FINISHED |
| Object | to prepare Parikshit for death |
—
|
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: to prepare Parikshit for death | Statement: [Suka, narrationPurpose, to prepare Parikshit for death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrationPurpose Context triple: [Suka, narrationPurpose, to prepare Parikshit for death]
-
A.
narrativePurpose
chosen
Indicates the role or function that something serves within the structure or progression of a narrative.
-
B.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
C.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
D.
narratesAs
Indicates that one entity tells, recounts, or presents a story, event, or information in the manner, style, or voice of another entity.
-
E.
narrationRequired
Indicates that an accompanying explanatory or descriptive narrative is required to properly present or understand the related content or event.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66766e46c81908721fd47066dc9f8 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.