Triple
T21461566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya orbit |
E529484
|
entity |
| Predicate | typicalEccentricity |
P2030
|
FINISHED |
| Object | high eccentricity |
—
|
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: high eccentricity | Statement: [Molniya orbit, typicalEccentricity, high eccentricity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEccentricity Context triple: [Molniya orbit, typicalEccentricity, high eccentricity]
-
A.
isEccentric
Indicates that an entity behaves or appears in a way that deviates noticeably from conventional or expected norms.
-
B.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
C.
eccentricityClass
Indicates the classification of how unconventional or atypical an entity’s behavior, properties, or characteristics are relative to a defined norm.
-
D.
hasEccentricity
chosen
Indicates that an object or orbit possesses a specific degree of deviation from being perfectly circular, quantified by its eccentricity value.
-
E.
hasEccentricityPeriod
Indicates a relationship where an object is associated with a specific orbital eccentricity and its corresponding orbital period.
- 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.