Triple
T35087550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok D upper stage |
E1012617
|
entity |
| Predicate | orbitFromWhichItOperates |
P7214
|
FINISHED |
| Object | low Earth parking 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 parking orbit | Statement: [Blok D upper stage, orbitFromWhichItOperates, low Earth parking orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitFromWhichItOperates Context triple: [Blok D upper stage, orbitFromWhichItOperates, low Earth parking orbit]
-
A.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
B.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
isPartOfTransportOrbital
Indicates that one orbital path or segment belongs to, or functions as a component within, a larger transport-related orbital trajectory or system.
-
D.
typeOfSatelliteOperated
Indicates that one entity operates or manages a satellite of a specified type or category in relation to another entity.
-
E.
operatesOnSatellite
Indicates that an entity performs operations or exercises control over a satellite.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.