Triple
T10183738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta IV Heavy |
E236854
|
entity |
| Predicate | successfullyLaunchedOrion |
P92573
|
FINISHED |
| Object | 2014-12-05 |
—
|
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: 2014-12-05 | Statement: [Delta IV Heavy, successfullyLaunchedOrion, 2014-12-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successfullyLaunchedOrion Context triple: [Delta IV Heavy, successfullyLaunchedOrion, 2014-12-05]
-
A.
successfullyReachedOrbitOnVehicle
Indicates that an entity has successfully achieved orbit using a specified launch vehicle.
-
B.
successfulLaunches
Indicates that one entity has carried out one or more launches that achieved their intended objectives without failure.
-
C.
firstOrbitalSuccessPayloadType
Indicates the type or category of payload carried on an entity’s first successful orbital mission.
-
D.
relaunchOrbit
Indicates that an entity is placed back into orbit after having previously left or ceased its orbital path.
-
E.
firstOrbitalMissionOutcome
Indicates the result or status achieved by an entity’s first orbital mission.
- 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.