Triple
T25750406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis |
E648455
|
entity |
| Predicate | reentryIncident |
P105637
|
FINISHED |
| Object | crash landing due to parachute failure |
—
|
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: crash landing due to parachute failure | Statement: [Genesis, reentryIncident, crash landing due to parachute failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryIncident Context triple: [Genesis, reentryIncident, crash landing due to parachute failure]
-
A.
reentryOutcome
chosen
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
B.
reentryCause
Indicates the factor, event, or condition that led to or triggered a reentry.
-
C.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
-
D.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
E.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd7df2ac8190a206646c8640cec0 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 4:34 a.m.