Triple
T21461632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok-L |
E529485
|
entity |
| Predicate | orbitTypeTargeted |
P96574
|
FINISHED |
| Object | highly elliptical 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: highly elliptical orbit | Statement: [Blok-L, orbitTypeTargeted, highly elliptical orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitTypeTargeted Context triple: [Blok-L, orbitTypeTargeted, highly elliptical orbit]
-
A.
orbitReached
Indicates that an object has successfully arrived at and is now following its intended orbital path around a central body.
-
B.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
designedForOrbitType
chosen
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
-
D.
targetOrbitInclination
Indicates the angle between an object's orbital plane and a reference plane (such as the equatorial or ecliptic plane) for its target orbit.
-
E.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
- 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_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. |
Created at: April 16, 2026, 6:09 p.m.