Triple
T4080329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanguard TV-4 |
E87461
|
entity |
| Predicate | launchVehicleRole |
P52887
|
FINISHED |
| Object | test 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: test vehicle | Statement: [Vanguard TV-4, launchVehicleRole, test vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleRole Context triple: [Vanguard TV-4, launchVehicleRole, test vehicle]
-
A.
launchVehicle
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.
-
B.
launchVehicleSupported
Indicates that one entity provides the necessary infrastructure, capability, or compatibility to support the operation or use of a particular launch vehicle.
-
C.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
D.
usesLaunchVehicleBooster
Indicates that a launch vehicle employs a specific booster as part of its propulsion system during launch.
-
E.
launchVehicleType
Indicates the type or category of launch vehicle used to carry a payload or mission into space.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9b34dec81909bbc3def9decc71a |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:39 p.m.