Triple
T38218681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M41A pulse rifle |
E1010750
|
entity |
| Predicate | hasIntegratedWeapon |
P6014
|
FINISHED |
| Object | pump‑action grenade launcher |
—
|
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: pump‑action grenade launcher | Statement: [M41A pulse rifle, hasIntegratedWeapon, pump‑action grenade launcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntegratedWeapon Context triple: [M41A pulse rifle, hasIntegratedWeapon, pump‑action grenade launcher]
-
A.
hasCannon
Indicates that one entity is equipped with, contains, or features a cannon.
-
B.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
hasAmmunitionStorage
Indicates that an entity possesses or is associated with a designated place or facility for storing ammunition.
-
D.
weaponryCarried
Indicates that one entity is carrying or equipped with a weapon or set of weapons in relation to another entity or context.
-
E.
hasEnergyWeapons
Indicates that an entity is equipped with or uses weapons that emit or manipulate energy (such as lasers or plasma) rather than conventional physical projectiles.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: May 3, 2026, 4:30 p.m.