Triple
T27549149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir EO-23 |
E695442
|
entity |
| Predicate | spaceStationOrbit |
P168949
|
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: [Mir EO-23, spaceStationOrbit, Low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceStationOrbit Context triple: [Mir EO-23, spaceStationOrbit, Low Earth orbit]
-
A.
positionOnISS
Indicates that one entity occupies a specific location or role on the International Space Station relative to other entities or reference points.
-
B.
spaceStationName
Indicates that an entity has the specified name of a space station.
-
C.
orbiterStatus
Indicates the current operational or mission state of an orbiting spacecraft relative to its target body or mission phase.
-
D.
spaceStationReentryDate
Indicates the date on which a space station reenters the Earth's atmosphere or is deorbited.
-
E.
spaceStationAssociation
Indicates an affiliation or operational relationship between an entity and a specific space station, such as ownership, management, use, or service connection.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 1:34 p.m.