Triple
T33584518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W62 warhead |
E860242
|
entity |
| Predicate | laterSuccessorOnMinutemanIII |
P200664
|
FINISHED |
| Object | W87 warhead |
—
|
NE NERFINISHED |
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: W87 warhead | Statement: [W62 warhead, laterSuccessorOnMinutemanIII, W87 warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSuccessorOnMinutemanIII Context triple: [W62 warhead, laterSuccessorOnMinutemanIII, W87 warhead]
-
A.
successorOnMinutemanIII
chosen
Indicates that one entity serves as the successor to another in the context of the Minuteman III missile system.
-
B.
successorCaliber
Indicates that one entity serves as the successor or follow-up version in terms of quality, standard, or specification relative to another.
-
C.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
D.
modernSuccessorUnit
Indicates that one unit is the contemporary or currently existing successor to another, carrying forward its role, function, or lineage in a modern context.
-
E.
successorAsMinor
Indicates that one entity becomes the next holder of a role, title, or position while still legally a minor.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 1, 2026, 1:40 a.m.