Triple
T28310226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTR-91 |
E713972
|
entity |
| Predicate | chamberSupport |
P9006
|
FINISHED |
| Object | designed for 7.62×51mm NATO pressure levels |
—
|
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: designed for 7.62×51mm NATO pressure levels | Statement: [PTR-91, chamberSupport, designed for 7.62×51mm NATO pressure levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberSupport Context triple: [PTR-91, chamberSupport, designed for 7.62×51mm NATO pressure levels]
-
A.
chamberSupportedBy
Indicates that a chamber is physically held up, carried, or structurally sustained by another object or structure.
-
B.
forChamber
Indicates that something is intended for use in, associated with, or belonging to a particular chamber.
-
C.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
D.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
E.
chamberedFor
chosen
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
- 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_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:40 p.m.