Triple

T8189564
Position Surface form Disambiguated ID Type / Status
Subject Pattern 1914 Enfield rifle E191269 entity
Predicate chamberingChangeReason P5019 FINISHED
Object standardization on .303 British 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: standardization on .303 British | Statement: [Pattern 1914 Enfield rifle, chamberingChangeReason, standardization on .303 British]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: chamberingChangeReason
Context triple: [Pattern 1914 Enfield rifle, chamberingChangeReason, standardization on .303 British]
  • A. changeReason chosen
    Indicates the reason or justification for a modification or change made to an entity or its state.
  • B. chamberedFor
    Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
  • C. reasonForChange
    Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
  • D. chamber2
    Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
  • E. chamber1
    Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
  • 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_69ca82c5b6948190a583c096fb0a6c71 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4da0e1288190b9c7c1d3b9a98830 completed March 31, 2026, 4:29 a.m.
PD Predicate disambiguation batch_69cb36aac86081909b83636e352e0ced completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:41 p.m.