Triple
T37997029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC-40 |
E947987
|
entity |
| Predicate | launchVehiclePreviouslySupported |
P30131
|
FINISHED |
| Object | Titan III |
—
|
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: Titan III | Statement: [SLC-40, launchVehiclePreviouslySupported, Titan III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehiclePreviouslySupported Context triple: [SLC-40, launchVehiclePreviouslySupported, Titan III]
-
A.
launchVehicleSupported
chosen
Indicates that one entity provides the necessary infrastructure, capability, or compatibility to support the operation or use of a particular launch vehicle.
-
B.
formerLaunchVehicle
Indicates that an entity was previously used as a launch vehicle but is no longer in active service or operation.
-
C.
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.
-
D.
launchVehicleProvider
Indicates the entity that supplies or operates the launch vehicle used to carry a payload into space.
-
E.
lastLaunchVehicle
Indicates that one entity is the most recent launch vehicle used to carry or deploy the other entity.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:20 p.m.