Triple
T19699011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karna–Arjuna duel |
E473040
|
entity |
| Predicate | hasOutcomeForWar |
P33358
|
FINISHED |
| Object | turningPointAgainstKauravas |
—
|
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: turningPointAgainstKauravas | Statement: [Karna–Arjuna duel, hasOutcomeForWar, turningPointAgainstKauravas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeForWar Context triple: [Karna–Arjuna duel, hasOutcomeForWar, turningPointAgainstKauravas]
-
A.
hasMajorAllianceOutcome
Indicates that a major alliance results in, or leads to, a specific significant outcome or consequence.
-
B.
hasPrimaryBelligerentDefeated
Indicates that the primary belligerent in a conflict or confrontation has been defeated by another party.
-
C.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
D.
hasConquered
Indicates that one entity has taken control over another entity or its territory through force or domination.
-
E.
hasEventOutcome
chosen
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b426608190a46abec3652a6ca0 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.