Triple
T4424345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prompt Global Strike |
E95174
|
entity |
| Predicate | weaponTypeConsidered |
P16410
|
FINISHED |
| Object | hypersonic glide vehicle |
—
|
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: hypersonic glide vehicle | Statement: [Prompt Global Strike, weaponTypeConsidered, hypersonic glide vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponTypeConsidered Context triple: [Prompt Global Strike, weaponTypeConsidered, hypersonic glide vehicle]
-
A.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
-
B.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
C.
weaponCategory
chosen
Indicates the classification or type of weapon to which an item or armament belongs.
-
D.
weaponTypeDelivered
Indicates that a specific type of weapon has been delivered from one entity to another.
-
E.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554ca5208190ba2661616dcf071c |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.