Triple
T12735492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 1 |
E304351
|
entity |
| Predicate | reentryCause |
P106631
|
FINISHED |
| Object | insufficient velocity for lunar transfer |
—
|
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: insufficient velocity for lunar transfer | Statement: [Pioneer 1, reentryCause, insufficient velocity for lunar transfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryCause Context triple: [Pioneer 1, reentryCause, insufficient velocity for lunar transfer]
-
A.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
B.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
C.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
D.
reentryModule
Indicates that one entity serves as the reentry module or component used for returning from space or a high-altitude environment.
-
E.
reentryObjective
Indicates that an action or plan is aimed at achieving a specific goal related to reentering a system, environment, or domain.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.