Triple

T22503003
Position Surface form Disambiguated ID Type / Status
Subject Royal New Zealand Army Logistic Regiment E556321 entity
Predicate supports P516 FINISHED
Object Deployable Joint Task Force (Land) — NE NERFINISHED

How this triple was built (3 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: Deployable Joint Task Force (Land) | Statement: [Royal New Zealand Army Logistic Regiment, supports, Deployable Joint Task Force (Land)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Deployable Joint Task Force (Land)
Context triple: [Royal New Zealand Army Logistic Regiment, supports, Deployable Joint Task Force (Land)]
  • A. Rapid Deployment Joint Task Force
    The Rapid Deployment Joint Task Force was a U.S. military organization created in the late 1970s to provide a quickly deployable, multi-service force for crises in the Middle East and Southwest Asia.
  • B. Civilian Joint Task Force
    The Civilian Joint Task Force is a pro-government vigilante militia in northeastern Nigeria composed mainly of local civilians who assist security forces in combating the Boko Haram insurgency.
  • C. Rapid Deployment Force
    The Rapid Deployment Force is a specialized Colombian military unit designed for swift, high-mobility operations against insurgent and criminal threats across the country.
  • D. Joint Task Force 435
    Joint Task Force 435 was a U.S. military command responsible for overseeing detention and related operations in Afghanistan, including the management of key internment facilities.
  • E. Combined Joint Task Force 7
    Combined Joint Task Force 7 was a U.S.-led military headquarters responsible for overseeing coalition operations in Iraq during the early phase of the Iraq War.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Deployable Joint Task Force (Land)
Target entity description: The Deployable Joint Task Force (Land) is a New Zealand Defence Force land-based formation designed for rapid deployment and integrated operations across multiple military branches.
  • A. Rapid Deployment Joint Task Force
    The Rapid Deployment Joint Task Force was a U.S. military organization created in the late 1970s to provide a quickly deployable, multi-service force for crises in the Middle East and Southwest Asia.
  • B. Civilian Joint Task Force
    The Civilian Joint Task Force is a pro-government vigilante militia in northeastern Nigeria composed mainly of local civilians who assist security forces in combating the Boko Haram insurgency.
  • C. Rapid Deployment Force
    The Rapid Deployment Force is a specialized Colombian military unit designed for swift, high-mobility operations against insurgent and criminal threats across the country.
  • D. Joint Task Force 435
    Joint Task Force 435 was a U.S. military command responsible for overseeing detention and related operations in Afghanistan, including the management of key internment facilities.
  • E. Combined Joint Task Force 7
    Combined Joint Task Force 7 was a U.S.-led military headquarters responsible for overseeing coalition operations in Iraq during the early phase of the Iraq War.
  • F. None of above. chosen

Provenance (2 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d5a01888190ba65a05616b63cbe completed April 29, 2026, 1:22 a.m.
Created at: April 16, 2026, 8:50 p.m.