Triple
T24084006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exoatmospheric Kill Vehicle |
E596583
|
entity |
| Predicate | targetPhase |
P59737
|
FINISHED |
| Object | midcourse phase in space |
—
|
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 in space | Statement: [Exoatmospheric Kill Vehicle, targetPhase, midcourse phase in space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPhase Context triple: [Exoatmospheric Kill Vehicle, targetPhase, midcourse phase in space]
-
A.
targetsPhase
chosen
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
B.
latestPhase
Indicates the most recent stage or step reached in a process, lifecycle, or sequence of phases.
-
C.
approachingPhase
Indicates that one entity is moving closer to another entity or target, entering a phase of decreasing distance or separation.
-
D.
campaignPhase
Indicates the specific stage or period within the lifecycle of a campaign in which an entity or activity currently occurs.
-
E.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
- 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.