Triple
T28067347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merlin Vacuum |
E709290
|
entity |
| Predicate | associatedLaunchVehicle |
P202700
|
FINISHED |
| Object | Falcon 9 |
—
|
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: Falcon 9 | Statement: [Merlin Vacuum, associatedLaunchVehicle, Falcon 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLaunchVehicle Context triple: [Merlin Vacuum, associatedLaunchVehicle, Falcon 9]
-
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.
lastLaunchVehicle
Indicates that one entity is the most recent launch vehicle used to carry or deploy the other entity.
-
C.
spacecraftLaunchAssociatedWith
Indicates a relationship where a spacecraft launch is connected or linked to another event, object, or entity involved in or affected by that launch.
-
D.
usedLaunchVehicleType
Indicates that a particular launch or mission was carried out using a launch vehicle of the specified type.
-
E.
formerLaunchVehicle
Indicates that an entity was previously used as a launch vehicle but is no longer in active service or operation.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_6a00ae622d9c81909815b10ed11cddfe |
completed | May 10, 2026, 4:12 p.m. |
Created at: April 27, 2026, 8:43 p.m.