Triple
T33839563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 landing site |
E867321
|
entity |
| Predicate | launchVehicleOfMission |
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: [Apollo 15 landing site, launchVehicleOfMission, Saturn V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleOfMission Context triple: [Apollo 15 landing site, launchVehicleOfMission, 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.
launchSpacecraft
Indicates initiating the sending of a spacecraft from a launch site into space, typically by activating and controlling its launch vehicle.
-
E.
launchVehicleComponentOf
Indicates that one entity is a component or part of a launch vehicle used to send payloads 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:47 a.m.