Triple

T31400160
Position Surface form Disambiguated ID Type / Status
Subject Khyber Pass operations E800974 entity
Predicate startInConflictPhase P104851 FINISHED
Object early phase of the Second Anglo-Afghan War 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: early phase of the Second Anglo-Afghan War | Statement: [Khyber Pass operations, startInConflictPhase, early phase of the Second Anglo-Afghan War]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: startInConflictPhase
Context triple: [Khyber Pass operations, startInConflictPhase, early phase of the Second Anglo-Afghan War]
  • A. usedInConflictPhase
    Indicates that an action, resource, or strategy is employed during a specific phase or stage of a conflict.
  • B. conflictBeginsFor chosen
    Indicates the point in time or event at which a conflict starts for a particular party or set of parties.
  • C. endedConflictPhase
    Indicates that a particular phase or stage within a broader conflict has come to an end.
  • D. implementedDuringConflict
    Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
  • E. followsConflictPhase
    Indicates that one conflict phase occurs after and is temporally subsequent to another conflict phase.
  • 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_69f224ea9998819086ae2e4f4f4091c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69ff2636e2bc8190bba91eff91431c6e completed May 9, 2026, 12:19 p.m.
PD Predicate disambiguation batch_69ff25c65be48190868480d94e1c4e89 completed May 9, 2026, 12:17 p.m.
Created at: April 29, 2026, 9:19 p.m.