Triple

T4949707
Position Surface form Disambiguated ID Type / Status
Subject Operation Impact E111138 entity
Predicate target P860 FINISHED
Object ISIS E133146 NE 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: ISIS | Statement: [Operation Impact, target, ISIS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISIS
Context triple: [Operation Impact, target, ISIS]
  • A. ISIS chosen
    ISIS is a violent extremist Islamist militant group known for establishing a self-proclaimed caliphate in parts of Iraq and Syria and carrying out widespread terrorist attacks.
  • B. IS
    IS is the two-letter ISO 3166-1 alpha-2 country code representing Iceland in international standards and systems.
  • C. ISA
    ISA (Industry Standard Architecture) is an early computer bus standard used in IBM PCs and compatible systems to connect expansion cards and peripherals to the motherboard.
  • D. ISA
    ISA is the common abbreviation for the Israel Security Agency, Israel’s domestic intelligence and security service responsible for counterterrorism and internal security.
  • E. ISA
    ISA is the IATA airport code for Mount Isa Airport, a regional airport serving the mining city of Mount Isa in Queensland, Australia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd441721cc819085c7e33fe0876818 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7167f97481908db5bfa9338e3824 completed March 20, 2026, 4:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69be81d03b088190aa6601298ee4d8fd completed March 21, 2026, 11:32 a.m.
Created at: March 20, 2026, 1:31 p.m.