Triple

T25945559
Position Surface form Disambiguated ID Type / Status
Subject Dutchbat E653829 entity
Predicate airSupportOutcome P6269 FINISHED
Object insufficient and delayed air strikes 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: insufficient and delayed air strikes | Statement: [Dutchbat, airSupportOutcome, insufficient and delayed air strikes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: airSupportOutcome
Context triple: [Dutchbat, airSupportOutcome, insufficient and delayed air strikes]
  • A. airSupport chosen
    Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
  • B. airSupportPlannedFrom
    Indicates that air support operations are scheduled or intended to be provided starting from a specified source or location.
  • C. airLegType
    Indicates the specific type or category of an air travel segment within an itinerary (e.g., flight leg classification or role).
  • D. airService
    Indicates that an air transportation service (such as flights or air routes) is provided or operates between the related entities.
  • E. airServiceType
    Indicates the specific category or nature of an air transportation service provided or used in the relationship.
  • 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_69e7ab40ac788190a771bc499eb1ae5f completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f60464d4988190bc39b78c8e418547 completed May 2, 2026, 2:04 p.m.
PD Predicate disambiguation batch_69f4a10480748190a2e67bd399fc435d completed May 1, 2026, 12:48 p.m.
Created at: April 22, 2026, 8:43 a.m.