Triple

T28310658
Position Surface form Disambiguated ID Type / Status
Subject Program Executive Office Ammunition E713982 entity
Predicate typeOfAmmunitionManaged P6074 FINISHED
Object conventional ammunition 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: conventional ammunition | Statement: [Program Executive Office Ammunition, typeOfAmmunitionManaged, conventional ammunition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfAmmunitionManaged
Context triple: [Program Executive Office Ammunition, typeOfAmmunitionManaged, conventional ammunition]
  • A. ammunitionType chosen
    Indicates the specific kind or category of ammunition associated with or used by an entity.
  • B. ammunitionCapacity
    Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
  • C. hasAmmunitionStorage
    Indicates that an entity possesses or is associated with a designated place or facility for storing ammunition.
  • D. rangeStandardAmmunition
    Indicates that the relationship specifies the standard type of ammunition used for a given range or weapon system.
  • E. armamentCapacity
    Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
  • 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_69efb5256afc8190b9322d25c3ae6320 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69fe7eb4b8348190bb19d35766189ed4 completed May 9, 2026, 12:24 a.m.
PD Predicate disambiguation batch_69fe7c35d2148190ab952e54feda1e76 completed May 9, 2026, 12:13 a.m.
Created at: April 27, 2026, 11:40 p.m.