Triple
T24083976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exoatmospheric Kill Vehicle |
E596583
|
entity |
| Predicate | operatingPhase |
P22825
|
FINISHED |
| Object | midcourse phase of ballistic missile trajectory |
—
|
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: midcourse phase of ballistic missile trajectory | Statement: [Exoatmospheric Kill Vehicle, operatingPhase, midcourse phase of ballistic missile trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingPhase Context triple: [Exoatmospheric Kill Vehicle, operatingPhase, midcourse phase of ballistic missile trajectory]
-
A.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
B.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
C.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
D.
governancePhase
Indicates the specific stage or phase an entity is in within a broader governance or decision-making process.
-
E.
acquisitionPhase
Indicates the stage or phase within an overall acquisition process in which the related entities are currently involved.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc279ac48190b60a0753981f0b97 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.