Triple
T15016090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W76 thermonuclear warhead |
E377962
|
entity |
| Predicate | lifeExtensionProgramName |
P116376
|
FINISHED |
| Object | W76-1 LEP |
—
|
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: W76-1 LEP | Statement: [W76 thermonuclear warhead, lifeExtensionProgramName, W76-1 LEP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeExtensionProgramName Context triple: [W76 thermonuclear warhead, lifeExtensionProgramName, W76-1 LEP]
-
A.
isForLife
Indicates that something is intended to last or remain valid for the entire duration of a person’s or entity’s life.
-
B.
givesLifeTo
Indicates a relationship where one entity causes, enables, or sustains the existence, vitality, or functioning of another.
-
C.
extendsProgramsOf
Indicates that one program builds upon, enhances, or broadens the scope of another program’s content, features, or capabilities.
-
D.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
E.
extendsProgramme
Indicates that one programme builds upon, continues, or expands the scope or content of another programme.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7633fcc8190b2231f43252bc46f |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.