Triple
T4959858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drona Parva |
E111376
|
entity |
| Predicate | chronologicalPositionInMahabharata |
P10630
|
FINISHED |
| Object | fourth war book |
—
|
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: fourth war book | Statement: [Drona Parva, chronologicalPositionInMahabharata, fourth war book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInMahabharata Context triple: [Drona Parva, chronologicalPositionInMahabharata, fourth war book]
-
A.
hasPositionInMahabharata
Indicates that one entity holds or is assigned a specific role, rank, or position within the context of the Mahabharata narrative.
-
B.
chronologicalPosition
chosen
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
viewOnMahabharata
Indicates a stance, interpretation, or perspective that someone holds regarding the Mahabharata.
-
D.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
E.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.