Triple
T4959794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duryodhana |
E111375
|
entity |
| Predicate | instigated |
P1408
|
FINISHED |
| Object | exile of the Pandavas for 13 years |
—
|
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: exile of the Pandavas for 13 years | Statement: [Duryodhana, instigated, exile of the Pandavas for 13 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instigated Context triple: [Duryodhana, instigated, exile of the Pandavas for 13 years]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
invade
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
C.
possiblyInitiatedBy
Indicates that an event or state may have been initiated or caused by a particular entity, but this initiating role is uncertain or not definitively established.
-
D.
inaugurated
Indicates that a person is formally introduced or installed into an official position, office, or role through a ceremonial event.
-
E.
initiatedBy
chosen
Indicates that an action, event, or process was started or set in motion by a particular 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_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.