Triple
T24083995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exoatmospheric Kill Vehicle |
E596583
|
entity |
| Predicate | destructionMechanism |
P71002
|
FINISHED |
| Object | kinetic energy |
—
|
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: kinetic energy | Statement: [Exoatmospheric Kill Vehicle, destructionMechanism, kinetic energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructionMechanism Context triple: [Exoatmospheric Kill Vehicle, destructionMechanism, kinetic energy]
-
A.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
B.
killMechanism
chosen
Indicates the method or process by which one entity causes the death or destruction of another.
-
C.
explosionMechanism
Indicates the specific process or mechanism by which an explosion is initiated or occurs.
-
D.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc279ac48190b60a0753981f0b97 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.