Triple
T16692456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orb-1 |
E405627
|
entity |
| Predicate | deorbitDisposal |
P57630
|
FINISHED |
| Object | destructive reentry |
—
|
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: destructive reentry | Statement: [Orb-1, deorbitDisposal, destructive reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deorbitDisposal Context triple: [Orb-1, deorbitDisposal, destructive reentry]
-
A.
deorbitMethod
chosen
Indicates the technique or process used to remove an object from orbit or bring it out of its orbital trajectory.
-
B.
deorbitCapability
Indicates the ability of an object (typically a spacecraft or satellite) to intentionally leave orbit and re-enter an atmosphere or otherwise deorbit in a controlled manner.
-
C.
deorbited
Indicates that an object has been intentionally or unintentionally removed from its orbit, typically causing it to reenter an atmosphere or otherwise cease orbiting.
-
D.
deorbitedWith
Indicates that one object’s orbit was intentionally or unintentionally lowered or terminated using another specified object, method, or system.
-
E.
spacecraftReentry
Indicates the event or process of a spacecraft returning from space and re-entering a planetary 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eaacb948190954231c9e97a4adf |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.