Triple
T4643244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 03 Chū-SAM |
E101703
|
entity |
| Predicate | launcherMissileCapacity |
P49953
|
FINISHED |
| Object | 6 missiles per 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: 6 missiles per launcher | Statement: [Type 03 Chū-SAM, launcherMissileCapacity, 6 missiles per launcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launcherMissileCapacity Context triple: [Type 03 Chū-SAM, launcherMissileCapacity, 6 missiles per launcher]
-
A.
armamentCapacity
chosen
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
-
B.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
C.
peakMissileInventory
Indicates the maximum number of missiles held in inventory at any point within a specified period or scenario.
-
D.
approximateNumberOfMissilesEliminated
Indicates the estimated quantity of missiles that have been neutralized or removed.
-
E.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a93047c8190990c94fd5a57c867 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.