Triple
T31989519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vz. 58 rifle |
E816824
|
entity |
| Predicate | boltCarrierDesign |
P81406
|
FINISHED |
| Object | lightweight bolt carrier |
—
|
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: lightweight bolt carrier | Statement: [vz. 58 rifle, boltCarrierDesign, lightweight bolt carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boltCarrierDesign Context triple: [vz. 58 rifle, boltCarrierDesign, lightweight bolt carrier]
-
A.
boltDesign
chosen
Indicates a design relationship where one entity specifies or defines the bolt configuration, features, or parameters used in another entity.
-
B.
bulletDesignation
Indicates that one entity is designated or labeled as a specific bullet point or bullet-style marker in relation to another entity.
-
C.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
-
D.
beltDesignOwner
Indicates that a particular entity is the owner or rights holder of a specific belt design.
-
E.
batteryDesignation
Indicates that one entity is designated or classified as a specific type or model of battery in relation to another entity.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b3c128819088fbbf04ffb3b3ec |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.