Triple
T33584517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W62 warhead |
E860242
|
entity |
| Predicate | successorOnMinutemanIII |
P200664
|
FINISHED |
| Object | W78 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: W78 warhead | Statement: [W62 warhead, successorOnMinutemanIII, W78 warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOnMinutemanIII Context triple: [W62 warhead, successorOnMinutemanIII, W78 warhead]
-
A.
successorCaliber
Indicates that one entity serves as the successor or follow-up version in terms of quality, standard, or specification relative to another.
-
B.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
C.
successorModel
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
D.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
-
E.
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.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 1, 2026, 1:40 a.m.