Triple
T17349006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M203 40 mm grenade launcher |
E421756
|
entity |
| Predicate | hasBarrel |
P127138
|
FINISHED |
| Object | rifled |
—
|
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 | Statement: [M203 40 mm grenade launcher, hasBarrel, rifled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBarrel Context triple: [M203 40 mm grenade launcher, hasBarrel, rifled]
-
A.
hasBarrelConfiguration
Indicates a relationship where an object is characterized by or assigned a specific arrangement or configuration of its barrel or barrels.
-
B.
hasBarrelLongerThan
Indicates that one entity’s barrel length is greater than that of another entity.
-
C.
hasHeavierBarrelThan
Indicates that the barrel of one entity has a greater weight than the barrel of another entity.
-
D.
barrelLengthVariants
Indicates that one entity has different versions or configurations distinguished by variations in barrel length.
-
E.
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.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2af5f88190b4c292ca30993b36 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.