Triple
T21461600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya orbit |
E529484
|
entity |
| Predicate | requiresStationKeeping |
P144429
|
FINISHED |
| Object | to maintain orbital parameters over time |
—
|
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: to maintain orbital parameters over time | Statement: [Molniya orbit, requiresStationKeeping, to maintain orbital parameters over time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresStationKeeping Context triple: [Molniya orbit, requiresStationKeeping, to maintain orbital parameters over time]
-
A.
keptOn
Indicates that one entity is stored, placed, or maintained on the surface or location of another entity over a period of time.
-
B.
continuesToHost
Indicates that an entity remains the host of another entity or event over an ongoing period of time.
-
C.
ownedStation
Indicates that one entity possesses ownership or control over a particular station.
-
D.
stillMaintained
Indicates that the subject continues to be actively maintained or supported over time.
-
E.
maintainsThrough
Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ef0c0881908554977df00604a6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:09 p.m.