Triple

T33832101
Position Surface form Disambiguated ID Type / Status
Subject Miranshah E867129 entity
Predicate securityStatusHistory P54960 FINISHED
Object designated conflict-affected area in the War on Terror 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: designated conflict-affected area in the War on Terror | Statement: [Miranshah, securityStatusHistory, designated conflict-affected area in the War on Terror]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityStatusHistory
Context triple: [Miranshah, securityStatusHistory, designated conflict-affected area in the War on Terror]
  • A. securityHistory chosen
    Indicates a record of past security-related events, states, or changes associated with an entity.
  • B. securityStatus
    Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
  • C. historicalStatusOf
    Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
  • D. historicalRecordStatus
    Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
  • E. securityBarrierStatus
    Indicates the current operational state or condition of a security barrier (e.g., whether it is active, inactive, open, closed, or otherwise engaged).
  • 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_69f34992ad40819087760ed939bd2a7a completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fcc4b700748190ae00b21d09c96695 completed May 7, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fcb0f9d3d881908a049475182fb039 completed May 7, 2026, 3:34 p.m.
Created at: May 1, 2026, 1:46 a.m.