Triple
T19278542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-48 |
E482120
|
entity |
| Predicate | UARSOrbitInclination |
P37302
|
FINISHED |
| Object | 57.0 degrees |
—
|
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: 57.0 degrees | Statement: [STS-48, UARSOrbitInclination, 57.0 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UARSOrbitInclination Context triple: [STS-48, UARSOrbitInclination, 57.0 degrees]
-
A.
targetOrbitInclination
chosen
Indicates the angle between an object's orbital plane and a reference plane (such as the equatorial or ecliptic plane) for its target orbit.
-
B.
orbitInclinationRange
Indicates the range of possible orbital inclination angles within which an object’s orbit is oriented relative to a reference plane.
-
C.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
D.
orbitalLongitude
Indicates the angular position of an orbiting body along its orbital path, measured as longitude from a defined reference direction or point.
-
E.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbe6e9c8190a7fa2ef3aa598e6c |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.