Triple
T21064619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David's Sling |
E518933
|
entity |
| Predicate | intendedToCounter |
P109536
|
FINISHED |
| Object | short-range ballistic missiles |
—
|
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: short-range ballistic missiles | Statement: [David's Sling, intendedToCounter, short-range ballistic missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedToCounter Context triple: [David's Sling, intendedToCounter, short-range ballistic missiles]
-
A.
counterplay
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
B.
counterMeasureAgainst
chosen
Indicates a relationship where one entity serves as a response or defensive action intended to prevent, mitigate, or neutralize the effects of another entity.
-
C.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
D.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
E.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb29e388190a80fa969a4daa606 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:44 p.m.