Triple

T4445165
Position Surface form Disambiguated ID Type / Status
Subject Special Operations Command Korea E96266 entity
Predicate militaryBranchCategory P4889 FINISHED
Object joint command 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: joint command | Statement: [Special Operations Command Korea, militaryBranchCategory, joint command]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryBranchCategory
Context triple: [Special Operations Command Korea, militaryBranchCategory, joint command]
  • A. militaryBranchAbbreviation
    Indicates the standard shortened form or acronym used to represent a specific branch of a military organization.
  • B. militaryBranchEmphasis
    Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
  • C. militaryOrganization chosen
    Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
  • D. hasMilitaryBranch
    Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
  • E. militaryBranchEligibility
    Indicates that an entity meets the required conditions to serve in a specified branch of the military.
  • 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_69b345415ba481908df738e7174448ba completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b355d00c288190a4f3fec29b5d85b2 completed March 13, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69b34f62c180819097ced38da2052207 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:32 p.m.