Triple
T13252659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 1 |
E315571
|
entity |
| Predicate | spacecraftReentry |
P109161
|
FINISHED |
| Object | decayed from orbit |
—
|
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: decayed from orbit | Statement: [Gemini 1, spacecraftReentry, decayed from orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftReentry Context triple: [Gemini 1, spacecraftReentry, decayed from orbit]
-
A.
spaceStationReentryLocation
Indicates the geographic location where a space station (or its remnants) reenters the Earth's atmosphere.
-
B.
spaceStationReentryDate
Indicates the date on which a space station reenters the Earth's atmosphere or is deorbited.
-
C.
spacecraftRecoveryBy
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
-
D.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
E.
associatedWithSpacecraftImpact
Indicates that an entity is related to, involved in, or results from the impact of a spacecraft.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:24 p.m.