Triple
T8189501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snider–Enfield rifle |
E191268
|
entity |
| Predicate | riflingType |
P53712
|
FINISHED |
| Object | progressive-depth rifling |
—
|
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: progressive-depth rifling | Statement: [Snider–Enfield rifle, riflingType, progressive-depth rifling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riflingType Context triple: [Snider–Enfield rifle, riflingType, progressive-depth rifling]
-
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.
rindType
Indicates the type or characteristic of the rind associated with an entity.
-
C.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
D.
barrelLengthInCalibers
Indicates the length of a barrel expressed as a multiple of its bore diameter (in calibers), describing how many times the bore diameter fits into the barrel length.
-
E.
hasDrillHolesFrom
Indicates that an object bears drill holes that were created by another specified entity or process.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da0e1288190b9c7c1d3b9a98830 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.