Triple
T36500976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gewehr 88 |
E899326
|
entity |
| Predicate | riflingSystem |
P53712
|
FINISHED |
| Object | rifled barrel with jacket sleeve |
—
|
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: rifled barrel with jacket sleeve | Statement: [Gewehr 88, riflingSystem, rifled barrel with jacket sleeve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riflingSystem Context triple: [Gewehr 88, riflingSystem, rifled barrel with jacket sleeve]
-
A.
rifling
chosen
Indicates the presence or action of spiral grooves inside a gun barrel that impart spin to a projectile to stabilize its flight.
-
B.
ammunitionFeedSystem
Indicates a mechanism or process by which ammunition is supplied or delivered to a weapon or firing system.
-
C.
firingSystemComponents
Indicates that certain components are part of, or belong to, a firing system used to initiate or control a firing action.
-
D.
isGasOperated
Indicates that an entity functions or operates using gas as its primary power or energy source.
-
E.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.