Triple
T16509783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBU-55 JDAM variant |
E401027
|
entity |
| Predicate | hasAttackProfile |
P123825
|
FINISHED |
| Object | medium altitude release |
—
|
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: medium altitude release | Statement: [GBU-55 JDAM variant, hasAttackProfile, medium altitude release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttackProfile Context triple: [GBU-55 JDAM variant, hasAttackProfile, medium altitude release]
-
A.
hasAttack
Indicates that one entity performs, possesses, or is associated with an attack directed toward another entity.
-
B.
attackProfile
Indicates a relationship where one entity initiates or carries out an aggressive or hostile action against another entity.
-
C.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
D.
numberOfAttacks
Indicates the count of distinct attack events associated with a given entity or interaction.
-
E.
hasPrimaryAttack
Indicates that an entity’s main or most frequently used offensive action is another specified entity or attack.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54f7508190804bbae4c9bc8fe3 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.