Triple
T13529200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuttle-Mir docking module |
E323087
|
entity |
| Predicate | orbitDestination |
P8449
|
FINISHED |
| Object | low Earth 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: low Earth orbit | Statement: [Shuttle-Mir docking module, orbitDestination, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitDestination Context triple: [Shuttle-Mir docking module, orbitDestination, low Earth orbit]
-
A.
spacecraftDestination
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
B.
orbitReached
Indicates that an object has successfully arrived at and is now following its intended orbital path around a central body.
-
C.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
-
D.
hostSpaceAgency
Indicates that one entity serves as the space agency that organizes, manages, or officially represents space-related activities for another entity (such as a mission, event, or facility).
-
E.
spaceLaunchDestination
chosen
Indicates the target location or body in space toward which a space launch is directed.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafba2c308190873efd15dfe26358 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.