Triple
T18239115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peacekeeper ICBM |
E436759
|
entity |
| Predicate | MIRVCapacity |
P80385
|
FINISHED |
| Object | up to 10 warheads |
—
|
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: up to 10 warheads | Statement: [Peacekeeper ICBM, MIRVCapacity, up to 10 warheads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MIRVCapacity Context triple: [Peacekeeper ICBM, MIRVCapacity, up to 10 warheads]
-
A.
missionBayCapacity
Indicates the capacity or maximum volume that Mission Bay can hold or accommodate.
-
B.
unitCapacity
chosen
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
C.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e19d9881908d6a227528241e4a |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.