Triple

T32307676
Position Surface form Disambiguated ID Type / Status
Subject Battle Efficiency "E" E825410 entity
Predicate wearableInsignia P9510 FINISHED
Object ribbon or device worn by eligible personnel 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: ribbon or device worn by eligible personnel | Statement: [Battle Efficiency "E", wearableInsignia, ribbon or device worn by eligible personnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wearableInsignia
Context triple: [Battle Efficiency "E", wearableInsignia, ribbon or device worn by eligible personnel]
  • A. wearsInsigniaAt
    Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
  • B. hasInsigniaWornBy chosen
    Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
  • C. hasInsigniaComponent
    Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
  • D. rankInsigniaWornOn
    Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
  • E. protectiveEmblemName
    Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
  • 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_69f3491213b88190a57094d8697a7455 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bd8835588190b562ff2832f98acf completed May 3, 2026, 3:14 a.m.
PD Predicate disambiguation batch_69f6b632cf788190a3d0c08cd026b84b completed May 3, 2026, 2:42 a.m.
Created at: May 1, 2026, 12:45 a.m.