Triple
T5230245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir |
E118091
|
entity |
| Predicate | deorbited |
P62516
|
FINISHED |
| Object | 2001-03-23 |
—
|
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: 2001-03-23 | Statement: [Mir, deorbited, 2001-03-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deorbited Context triple: [Mir, deorbited, 2001-03-23]
-
A.
deorbitMethod
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.
removedFromEarthBy
Indicates that an entity was taken away or extracted from Earth by another agent or process.
-
D.
hasOrbitalDecay
Indicates that one object’s orbit around another is gradually shrinking or degrading over time, typically due to forces like drag or gravitational interactions.
-
E.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0093a88190aba381ba3f761408 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7aff0244819085c4799793ed0185 |
completed | March 20, 2026, 4:51 p.m. |
Created at: March 20, 2026, 1:48 p.m.