Triple

T277965
Position Surface form Disambiguated ID Type / Status
Subject Auxiliary Territorial Service E5289 entity
Predicate permittedCombatRole P5518 FINISHED
Object none (officially non-combatant) 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: none (officially non-combatant) | Statement: [Auxiliary Territorial Service, permittedCombatRole, none (officially non-combatant)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: permittedCombatRole
Context triple: [Auxiliary Territorial Service, permittedCombatRole, none (officially non-combatant)]
  • A. militaryFunction
    Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
  • B. mainCombatant
    Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
  • C. militaryCharacteristic
    Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
  • D. warfareCapability
    Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
  • E. typeOfRole chosen
    Indicates that one entity specifies the kind or category of role that another entity holds or performs.
  • 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_69a257e6c8788190987dfe705ca2912a completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25dee7830819087f153769a8496b9 completed Feb. 28, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69a25b7480e881909399beccfc7ffb81 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:59 a.m.