Triple
T15700638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLU-116 |
E380582
|
entity |
| Predicate | designedToSurvive |
P20750
|
FINISHED |
| Object | high-impact deceleration on target |
—
|
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: high-impact deceleration on target | Statement: [BLU-116, designedToSurvive, high-impact deceleration on target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToSurvive Context triple: [BLU-116, designedToSurvive, high-impact deceleration on target]
-
A.
designedToWithstand
chosen
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
B.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
C.
designedToDefeat
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
D.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
-
E.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.