Triple
T17773878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W87 warhead |
E443711
|
entity |
| Predicate | propulsionContext |
P128882
|
FINISHED |
| Object | reentry vehicle payload |
—
|
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: reentry vehicle payload | Statement: [W87 warhead, propulsionContext, reentry vehicle payload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propulsionContext Context triple: [W87 warhead, propulsionContext, reentry vehicle payload]
-
A.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
B.
laterPropulsion
Indicates that one propulsion system, method, or event occurs after another in time.
-
C.
propulsionPlacement
Indicates the spatial or structural location where a propulsion system is installed or positioned relative to the object it drives.
-
D.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
E.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871af4248190aed2b3bd42433771 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:12 a.m.