Triple

T2312595
Position Surface form Disambiguated ID Type / Status
Subject Karabiner 98k E51991 entity
Predicate effectiveFiringRange P25150 FINISHED
Object 500 m with iron sights 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: 500 m with iron sights | Statement: [Karabiner 98k, effectiveFiringRange, 500 m with iron sights]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: effectiveFiringRange
Context triple: [Karabiner 98k, effectiveFiringRange, 500 m with iron sights]
  • A. rateOfFire
    Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
  • B. gunElevationRange
    Indicates the range of vertical angles through which a gun can be elevated or depressed relative to a reference plane.
  • C. fireControlFeature
    Indicates a relationship where an entity possesses or is associated with a capability or mechanism for directing, managing, or controlling the use of fire or weapon fire.
  • D. operationalRange chosen
    Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
  • E. frontArmorRange
    Indicates the range or extent of protective armor coverage on the front-facing side of an entity.
  • 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_69a88b0bb30c81908ded03b006d29387 completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc685f05481909c863b29d1f6bacd completed March 7, 2026, 6:32 a.m.
PD Predicate disambiguation batch_69abc58e88e481908733fdf79d3f8a15 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:49 p.m.