Triple
T5819800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K9A1 |
E129078
|
entity |
| Predicate | hasRangeType |
P8771
|
FINISHED |
| Object | extended range with base bleed 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: extended range with base bleed ammunition | Statement: [K9A1, hasRangeType, extended range with base bleed ammunition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRangeType Context triple: [K9A1, hasRangeType, extended range with base bleed ammunition]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
rangeType
chosen
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
C.
hasMajorRange
Indicates that one entity encompasses or defines the primary or most extensive range or scope associated with another entity.
-
D.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
hasGateRange
Indicates the range of values or interval within which a gate or gating parameter is valid or operates.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.