Triple
T29613570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OTO Melara 76/62 Super Rapid gun |
E754798
|
entity |
| Predicate | ammoHandling |
P56140
|
FINISHED |
| Object | automatic ammunition feed |
—
|
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: automatic ammunition feed | Statement: [OTO Melara 76/62 Super Rapid gun, ammoHandling, automatic ammunition feed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ammoHandling Context triple: [OTO Melara 76/62 Super Rapid gun, ammoHandling, automatic ammunition feed]
-
A.
ammunitionLoading
chosen
Indicates the action or process of placing ammunition into a weapon or storage system for use.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
hasAmmunitionStorage
Indicates that an entity possesses or is associated with a designated place or facility for storing ammunition.
-
D.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e1e5c5c81909acf808419a9e48f |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:30 p.m.