Triple
T4643237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 03 Chū-SAM |
E101703
|
entity |
| Predicate | batteryComposition |
P57557
|
FINISHED |
| Object | multiple launch vehicles |
—
|
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: multiple launch vehicles | Statement: [Type 03 Chū-SAM, batteryComposition, multiple launch vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryComposition Context triple: [Type 03 Chū-SAM, batteryComposition, multiple launch vehicles]
-
A.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
-
B.
batterySupplier
Indicates that one entity serves as the supplier or provider of batteries to another entity.
-
C.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
D.
batteryCapacity
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
-
E.
plannedMainBatteryConfiguration
Indicates the intended or designed primary weapon or main battery setup that was planned for an entity, typically before implementation or construction.
- 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_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. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:14 p.m.