Triple
T6472699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ground-based Midcourse Defense |
E145992
|
entity |
| Predicate | interceptorBasing |
P71001
|
FINISHED |
| Object | silo-based |
—
|
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: silo-based | Statement: [Ground-based Midcourse Defense, interceptorBasing, silo-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interceptorBasing Context triple: [Ground-based Midcourse Defense, interceptorBasing, silo-based]
-
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.
basingMode
Indicates the method or principle on which something is founded, justified, or determined.
-
D.
bindingFor
Indicates that one entity serves as the binding, constraint, or linkage mechanism that determines how another entity is associated, applied, or made effective.
-
E.
routingBasis
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a3188488190a1b7452ede91ba5e |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:50 p.m.