Triple
T33212092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OLA |
E850187
|
entity |
| Predicate | hostSpacecraftLaunchVehicle |
P100137
|
FINISHED |
| Object | Atlas V 411 |
—
|
NE NERFINISHED |
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: Atlas V 411 | Statement: [OLA, hostSpacecraftLaunchVehicle, Atlas V 411]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSpacecraftLaunchVehicle Context triple: [OLA, hostSpacecraftLaunchVehicle, Atlas V 411]
-
A.
coreLaunchVehicle
Indicates that one entity serves as the primary launch vehicle used to propel another entity (such as a payload or mission) into space.
-
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.
launchVehicleDesignation
chosen
Indicates the specific launch vehicle assigned or designated to carry a payload or mission into space.
-
D.
primaryLaunchVehicleForCargo
Indicates that a launch vehicle is the main rocket used to carry a specific cargo into space.
-
E.
usedLaunchVehicleType
Indicates that a particular launch or mission was carried out using a launch vehicle of the specified type.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:30 a.m.