Triple
T146040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypersonic Technology Vehicle programs |
E3331
|
entity |
| Predicate | launchMethod |
P4020
|
FINISHED |
| Object | rocket booster |
—
|
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: rocket booster | Statement: [Hypersonic Technology Vehicle programs, launchMethod, rocket booster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchMethod Context triple: [Hypersonic Technology Vehicle programs, launchMethod, rocket booster]
-
A.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
B.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
C.
launchVehicle
chosen
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
D.
distributionMethod
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
-
E.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ea7eac8190884a53453a9e0dd6 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a25656a4fc81908a87678ac3d28f93 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.