Triple
T20965295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | पाण्डु |
E516349
|
entity |
| Predicate | साहित्यिक स्रोत |
P10578
|
FINISHED |
| Object | महाभारत के आदिपर्व में वर्णित |
—
|
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: महाभारत के आदिपर्व में वर्णित | Statement: [पाण्डु, साहित्यिक स्रोत, महाभारत के आदिपर्व में वर्णित]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: साहित्यिक स्रोत Context triple: [पाण्डु, साहित्यिक स्रोत, महाभारत के आदिपर्व में वर्णित]
-
A.
literarySource
chosen
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
B.
hasLiterarySourceMedium
Indicates that something derives from, is based on, or is expressed through a particular literary medium (such as a book, poem, or script).
-
C.
literaryGenreOfSourceWork
Indicates that a work belongs to, or is characterized by, a particular literary genre.
-
D.
textSources
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
E.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb72ef4c8190bebdd2cef3c2148c |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.