Triple

T26460375
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kushk E665614 entity
Predicate almostCaused P160769 FINISHED
Object war between Russian Empire and British Empire 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: war between Russian Empire and British Empire | Statement: [Battle of Kushk, almostCaused, war between Russian Empire and British Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: almostCaused
Context triple: [Battle of Kushk, almostCaused, war between Russian Empire and British Empire]
  • A. possibleCauseOf
    Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
  • B. causeOf
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • C. eligibleCause
    Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
  • D. causeSupported
    Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
  • E. almostLedToWarIn
    Indicates that one entity’s actions or circumstances brought it very close to causing a war in a specified place or context, but the war ultimately did not occur.
  • F. None of above. chosen

Provenance (4 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_69ee883e812c8190a9b5a9cdb87fee5e completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f612946be8819080ae7c93980075b1 completed May 2, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69f602d5c8808190a1fdbebd6f0981e8 completed May 2, 2026, 1:57 p.m.
PDg Predicate description generation batch_69f604120e848190b516c29b781d19cc completed May 2, 2026, 2:02 p.m.
Created at: April 27, 2026, 12:12 a.m.