Triple
T32668282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ground Based Strategic Deterrent program |
E835216
|
entity |
| Predicate | successorSystemName |
P50932
|
FINISHED |
| Object | LGM-35A Sentinel |
—
|
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: LGM-35A Sentinel | Statement: [Ground Based Strategic Deterrent program, successorSystemName, LGM-35A Sentinel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorSystemName Context triple: [Ground Based Strategic Deterrent program, successorSystemName, LGM-35A Sentinel]
-
A.
successorSystem
chosen
Indicates that one system directly follows and replaces another in function, role, or version.
-
B.
successorPlannedName
Indicates that a new name has been planned to replace or succeed the current name.
-
C.
successorModel
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
D.
successorAdministrativeName
Indicates that one administrative entity’s name has been replaced by another name that now serves as its official administrative designation.
-
E.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 1, 2026, 1:08 a.m.