Triple

T1591666
Position Surface form Disambiguated ID Type / Status
Subject Resolute Support Mission E34189 entity
Predicate reductionOfScope P30064 FINISHED
Object followed the end of ISAF combat operations in 2014 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: followed the end of ISAF combat operations in 2014 | Statement: [Resolute Support Mission, reductionOfScope, followed the end of ISAF combat operations in 2014]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reductionOfScope
Context triple: [Resolute Support Mission, reductionOfScope, followed the end of ISAF combat operations in 2014]
  • A. scopeOfUse
    Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
  • B. reduces
    Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
  • C. scopeOfReset
    Indicates the range or extent within which a reset action applies or takes effect.
  • D. coverageScope
    Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
  • E. scopeType
    Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
  • F. None of above. chosen

Provenance (4 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_69a885fceb2c8190b47e0f7c0aefbff0 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93aedd45c819085843ac843d640e8 completed March 5, 2026, 8:12 a.m.
PD Predicate disambiguation batch_69a907bdc19081908c84c5c0aa09e282 completed March 5, 2026, 4:34 a.m.
PDg Predicate description generation batch_69a93aec7dc481909375726fbfb9e272 completed March 5, 2026, 8:12 a.m.
Created at: March 4, 2026, 7:27 p.m.