Triple
T4545213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir space station |
E110028
|
entity |
| Predicate | deorbitMethod |
P57630
|
FINISHED |
| Object | controlled 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: controlled reentry | Statement: [Mir space station, deorbitMethod, controlled reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deorbitMethod Context triple: [Mir space station, deorbitMethod, controlled reentry]
-
A.
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.
-
B.
designedForOrbitInsertion
Indicates that something is intended or configured to perform or facilitate the insertion of an object into orbit.
-
C.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
removedFromEarthBy
Indicates that an entity was taken away or extracted from Earth by another agent or process.
-
E.
leavesEarthWith
Indicates that one entity departs from Earth together with another entity, accompanying them in leaving the planet.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:05 p.m.