Triple

T2726672
Position Surface form Disambiguated ID Type / Status
Subject Combined Force Space Component Command E60208 entity
Predicate alliesSupported P13524 FINISHED
Object NATO allies 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: NATO allies | Statement: [Combined Force Space Component Command, alliesSupported, NATO allies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alliesSupported
Context triple: [Combined Force Space Component Command, alliesSupported, NATO allies]
  • A. allianceSupport chosen
    Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
  • B. alliesInWar
    Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
  • C. hasPoliticalAlly
    Indicates that one entity supports and cooperates with another in a political context, treating them as an ally in political activities or objectives.
  • D. alliedRecognition
    Indicates that one entity formally acknowledges another as an ally or partner in a cooperative relationship.
  • E. allianceStatus
    Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
  • 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_69ab4b75cd908190b691ef0d1801acda completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdace9f308190964a064859612cd6 completed March 7, 2026, 7:59 a.m.
PD Predicate disambiguation batch_69abd82586f88190a98f60d3247fe2d3 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:56 p.m.