Triple
T33901273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 Command and Service Module |
E869052
|
entity |
| Predicate | crewLaunchMass |
P53671
|
FINISHED |
| Object | approximately 30 metric tons |
—
|
LITERAL FINISHED |
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: approximately 30 metric tons | Statement: [Apollo 15 Command and Service Module, crewLaunchMass, approximately 30 metric tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLaunchMass Context triple: [Apollo 15 Command and Service Module, crewLaunchMass, approximately 30 metric tons]
-
A.
massAtLiftoff
Indicates the total mass an object or vehicle has at the moment it leaves the ground or launch platform.
-
B.
coreLaunchVehicle
Indicates that one entity serves as the primary launch vehicle used to propel another entity (such as a payload or mission) into space.
-
C.
spacecraftMass
chosen
Indicates the mass value associated with a spacecraft in a given context.
-
D.
primaryLaunchVehicleForCargo
Indicates that a launch vehicle is the main rocket used to carry a specific cargo into space.
-
E.
landingModuleMass
Indicates the mass of a landing module involved in a landing operation or configuration.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.