Triple
T35144095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I rifle |
E1014772
|
entity |
| Predicate | chamberingCompatibleWith |
P9006
|
FINISHED |
| Object | Type 38 rifle 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: Type 38 rifle ammunition | Statement: [Type I rifle, chamberingCompatibleWith, Type 38 rifle ammunition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberingCompatibleWith Context triple: [Type I rifle, chamberingCompatibleWith, Type 38 rifle ammunition]
-
A.
hasChamberSize
Indicates a relationship where an entity is associated with, or characterized by, a specific size of a chamber or internal compartment.
-
B.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
C.
chamberedFor
chosen
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
-
D.
hasChamberLength
Indicates the length measurement of a chamber associated with an entity.
-
E.
hasChamberWidth
Indicates that an entity possesses a chamber whose width has a specified value or range.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.