Triple

T12266645
Position Surface form Disambiguated ID Type / Status
Subject Airman Battle Uniform E292362 entity
Predicate successorUniform P78 FINISHED
Object Operational Camouflage Pattern uniform 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: Operational Camouflage Pattern uniform | Statement: [Airman Battle Uniform, successorUniform, Operational Camouflage Pattern uniform]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorUniform
Context triple: [Airman Battle Uniform, successorUniform, Operational Camouflage Pattern uniform]
  • A. successorPolicy
    Indicates that one policy follows or replaces another policy in a sequence or hierarchy.
  • B. successorUse
    Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
  • C. successor chosen
    Indicates that one entity directly follows another in an ordered sequence or position.
  • D. successorDeterminedBy
    Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
  • E. successorFunction
    Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
  • 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_69d6ab6856488190b5d31178d5015f8e completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d9380a5e78819086bd4dfe9a83d1f5 completed April 10, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69d91c4a66cc819083ce6fcaf5042af6 completed April 10, 2026, 3:50 p.m.
Created at: April 8, 2026, 9:52 p.m.