Triple
T8189604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1917 Enfield rifle |
E191270
|
entity |
| Predicate | boltDesign |
P81406
|
FINISHED |
| Object | Mauser-type rotating bolt |
—
|
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: Mauser-type rotating bolt | Statement: [M1917 Enfield rifle, boltDesign, Mauser-type rotating bolt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boltDesign Context triple: [M1917 Enfield rifle, boltDesign, Mauser-type rotating bolt]
-
A.
bladeType
Indicates the specific kind or category of blade associated with an object or entity.
-
B.
bellMounting
Indicates that one entity is mounted, fixed, or installed as a bell onto another supporting structure or surface.
-
C.
wheelArchDesign
Indicates the specific design or configuration of a vehicle’s wheel arch in relation to its body or wheel assembly.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
badgeEngineeredFrom
Indicates that a badge is derived, created, or generated based on another underlying source, design, or system.
- 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_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. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:41 p.m.