Triple
T10183718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta IV Heavy |
E236854
|
entity |
| Predicate | payloadToTransLunarInjection |
P92572
|
FINISHED |
| Object | about 10,000 kg |
—
|
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: about 10,000 kg | Statement: [Delta IV Heavy, payloadToTransLunarInjection, about 10,000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadToTransLunarInjection Context triple: [Delta IV Heavy, payloadToTransLunarInjection, about 10,000 kg]
-
A.
designedPayloadToLunarOrbit
Indicates that something was created or engineered specifically to deliver a payload into lunar orbit.
-
B.
MarsOrbitInsertion
Indicates the event or process of a spacecraft transitioning into a stable orbit around Mars.
-
C.
designedPayloadToLEO
Indicates that an object (typically a launch vehicle or system) is designed to deliver a specified payload mass to Low Earth Orbit (LEO).
-
D.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
E.
propellantTransferCapability
Indicates the ability of one entity to transfer propellant to or from another entity.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded3566f881909e0d1366f501d554 |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:12 p.m.