Triple
T22438993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond Arms Roughneck |
E554702
|
entity |
| Predicate | chamberingNote |
P148194
|
FINISHED |
| Object | varies by specific model configuration |
—
|
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: varies by specific model configuration | Statement: [Bond Arms Roughneck, chamberingNote, varies by specific model configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberingNote Context triple: [Bond Arms Roughneck, chamberingNote, varies by specific model configuration]
-
A.
chamberedFor
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
-
B.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
C.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
D.
chamberLevel
Indicates the relative position or height of a chamber within a larger structure or system.
-
E.
typicalChamber
Indicates that something is a standard or characteristic chamber associated with a given context or entity.
- F. None of above. chosen
Provenance (4 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae01bd08190aee5141f4c0848bc |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.