Triple
T902910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arjuna |
E19483
|
entity |
| Predicate | roleInKurukshetraWar |
P9987
|
FINISHED |
| Object | key warrior for the Pandavas |
—
|
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: key warrior for the Pandavas | Statement: [Arjuna, roleInKurukshetraWar, key warrior for the Pandavas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKurukshetraWar Context triple: [Arjuna, roleInKurukshetraWar, key warrior for the Pandavas]
-
A.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
roleInWarAndPeace
Indicates that an entity has a specific role or function within the context of the War and Peace conflict or narrative.
-
C.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad56f4c08190a7a5091ff0eb3209 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa98caec8190bbcc38320090f058 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.