Triple
T4836154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draupadi |
E108063
|
entity |
| Predicate | causeOfHumiliation |
P694
|
FINISHED |
| Object | dice game at Hastinapura |
—
|
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: dice game at Hastinapura | Statement: [Draupadi, causeOfHumiliation, dice game at Hastinapura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfHumiliation Context triple: [Draupadi, causeOfHumiliation, dice game at Hastinapura]
-
A.
insultedAs
Indicates that one entity directed an insulting or offensive remark or action toward another entity, characterizing the target in a demeaning way.
-
B.
causeOfReputation
Indicates that one entity is the reason or source for another entity’s reputation.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
correctsAberration
Indicates that one entity counteracts, fixes, or compensates for an error, flaw, or deviation present in another entity.
-
E.
subjectOfCondemnation
Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.