Triple
T11000822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ePOP |
E259997
|
entity |
| Predicate | hostSatelliteOrbitRegime |
P7214
|
FINISHED |
| Object | near-polar 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: near-polar low Earth orbit | Statement: [ePOP, hostSatelliteOrbitRegime, near-polar low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSatelliteOrbitRegime Context triple: [ePOP, hostSatelliteOrbitRegime, near-polar low Earth orbit]
-
A.
supportsOrbitRegimes
Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of 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.
typeOfSatelliteOperated
Indicates that one entity operates or manages a satellite of a specified type or category in relation to another entity.
-
D.
satelliteSystem
Indicates a relationship where one system functions as a satellite or subordinate system orbiting, supporting, or depending on another primary system.
-
E.
satelliteType
Indicates that one entity is classified as a specific type or category of satellite relative to another entity.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d68b608190a8d016b9383e82f8 |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.