Triple
T5416749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M230 30 mm chain gun |
E121150
|
entity |
| Predicate | typicalAmmunition |
P29553
|
FINISHED |
| Object | high-explosive incendiary |
—
|
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: high-explosive incendiary | Statement: [M230 30 mm chain gun, typicalAmmunition, high-explosive incendiary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAmmunition Context triple: [M230 30 mm chain gun, typicalAmmunition, high-explosive incendiary]
-
A.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
B.
typicalOrdnance
chosen
Indicates that something is a standard or commonly used type of weaponry or munitions associated with a given entity or context.
-
C.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
D.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
E.
ammunitionLoading
Indicates the action or process of placing ammunition into a weapon or storage system for use.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bff75881909bdfd2cdf7ff5657 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.