Triple
T23679013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Module 017 |
E584965
|
entity |
| Predicate | launchVehicleValidated |
P100137
|
FINISHED |
| Object | Saturn V |
—
|
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: Saturn V | Statement: [Service Module 017, launchVehicleValidated, Saturn V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleValidated Context triple: [Service Module 017, launchVehicleValidated, Saturn V]
-
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.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
C.
launchVehicleDesignation
chosen
Indicates the specific launch vehicle assigned or designated to carry a payload or mission into space.
-
D.
launchVehicleSupported
Indicates that one entity provides the necessary infrastructure, capability, or compatibility to support the operation or use of a particular launch vehicle.
-
E.
launchVehicleProvider
Indicates the entity that supplies or operates the launch vehicle used to carry a payload into space.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f5a7b48190b93d27416003e173 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.