Triple

T24084238
Position Surface form Disambiguated ID Type / Status
Subject Ground-Based Midcourse Defense E596588 entity
Predicate strategicCommandRelationship P75758 FINISHED
Object U.S. Northern Command NE NERFINISHED

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: U.S. Northern Command | Statement: [Ground-Based Midcourse Defense, strategicCommandRelationship, U.S. Northern Command]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strategicCommandRelationship
Context triple: [Ground-Based Midcourse Defense, strategicCommandRelationship, U.S. Northern Command]
  • A. alliedCommandRelationship
    Indicates a command relationship in which one entity exercises coordinated or subordinate authority in support of an allied or coalition partner’s operations.
  • B. strategicRelation
    Indicates a relationship where entities are connected through plans, goals, or coordinated actions intended to achieve long-term or high-level objectives.
  • C. strategicCommand chosen
    Indicates that one entity issues high-level, overarching directives or plans that guide the actions or decisions of another entity.
  • D. supremeAlliedCommanderRelationship
    Indicates a hierarchical military relationship in which one entity holds the role of Supreme Allied Commander with authority over allied forces or commanders.
  • E. numberOfStrategicCommands
    Indicates the quantity of strategic commands associated with or issued by a given entity.
  • 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_69e288c4638c81909bacc28a1e3d436b completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dc279ac48190b60a0753981f0b97 completed April 29, 2026, 10:23 a.m.
PD Predicate disambiguation batch_69f17651458c8190bbfd301883e46085 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 10:44 p.m.