Triple

T7009796
Position Surface form Disambiguated ID Type / Status
Subject 504th Military Intelligence Brigade E162551 entity
Predicate militaryBranchSpecialty P8360 FINISHED
Object military intelligence 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: military intelligence | Statement: [504th Military Intelligence Brigade, militaryBranchSpecialty, military intelligence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryBranchSpecialty
Context triple: [504th Military Intelligence Brigade, militaryBranchSpecialty, military intelligence]
  • A. militaryRole
    Indicates the specific function, position, or duty an entity holds within a military organization or context.
  • B. militaryBranchEmphasis chosen
    Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
  • C. militaryBranchEligibility
    Indicates that an entity meets the required conditions to serve in a specified branch of the military.
  • D. hasMilitaryBranch
    Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
  • E. militaryUnitTypeServed
    Indicates that an entity served in, or was a member of, a specific type of military unit.
  • 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_69c6885928148190ae31909fbb5e9849 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc38039c8190ab420d62bb11b4d9 completed March 27, 2026, 7:36 p.m.
PD Predicate disambiguation batch_69c6d7c790288190b7cbbaa4a5f9c91d completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:34 p.m.