Triple
T364132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope |
E7921
|
entity |
| Predicate | orbitInclination |
P9974
|
FINISHED |
| Object | 28.5 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: 28.5 degrees | Statement: [Hubble Space Telescope, orbitInclination, 28.5 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitInclination Context triple: [Hubble Space Telescope, orbitInclination, 28.5 degrees]
-
A.
orbitInclinationRange
Indicates the range of possible orbital inclination angles within which an object’s orbit is oriented relative to a reference plane.
-
B.
inclinationToEcliptic
chosen
Indicates the angle between an object's orbital plane and the plane of the ecliptic, describing how tilted its orbit is relative to Earth's orbital plane.
-
C.
inclinationToEarthEquator
Indicates the angle between an object's orbital or rotational plane and Earth's equatorial plane.
-
D.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
E.
galacticPlaneInclinationToEcliptic
Indicates the angle at which the galactic plane is tilted relative to the plane of the ecliptic.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.