Triple
T37720436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew Dragon In-Flight Abort Test |
E939567
|
entity |
| Predicate | spacecraftLanding |
P191141
|
FINISHED |
| Object | ocean splashdown |
—
|
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: ocean splashdown | Statement: [Crew Dragon In-Flight Abort Test, spacecraftLanding, ocean splashdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftLanding Context triple: [Crew Dragon In-Flight Abort Test, spacecraftLanding, ocean splashdown]
-
A.
planetaryBodyLandedOn
Indicates that one entity has successfully landed on the surface of a planetary body (such as a planet, moon, or asteroid).
-
B.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
C.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
D.
wasIntendedLandingSiteFor
Indicates that a particular location was designated or planned to be the landing site for a specific mission, vehicle, or object.
-
E.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 3, 2026, 4:18 p.m.