Triple
T18763461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SM-3 Block IIA |
E458833
|
entity |
| Predicate | interceptPhase |
P84870
|
FINISHED |
| Object | midcourse |
—
|
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 | Statement: [SM-3 Block IIA, interceptPhase, midcourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interceptPhase Context triple: [SM-3 Block IIA, interceptPhase, midcourse]
-
A.
designedToIntercept
Indicates that one entity is purposefully created or configured to detect, block, or otherwise interrupt the actions, movement, or effects of another entity.
-
B.
interceptionMethod
Indicates the technique or means by which an interception (such as capturing data, signals, or communications) is carried out.
-
C.
protocolPhase
chosen
Indicates the specific stage or step within a defined protocol or procedural sequence that an action, process, or entity is associated with.
-
D.
appliesToPhase
Indicates that a particular rule, condition, or action is relevant to and operates during a specific phase within a process or lifecycle.
-
E.
interceptingPlayer
Indicates that one player takes possession of or disrupts a pass, throw, or transmission intended for another player or target.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d80a954819083946dafc0c7af05 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.