Triple
T146023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypersonic Technology Vehicle programs |
E3331
|
entity |
| Predicate | vehicleTypeTested |
P1776
|
FINISHED |
| Object | unmanned hypersonic glide vehicle |
—
|
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: unmanned hypersonic glide vehicle | Statement: [Hypersonic Technology Vehicle programs, vehicleTypeTested, unmanned hypersonic glide vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleTypeTested Context triple: [Hypersonic Technology Vehicle programs, vehicleTypeTested, unmanned hypersonic glide vehicle]
-
A.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
B.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
C.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
hasCarLength
Indicates that an entity is associated with a specific measurement representing the length of a car.
- 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.