Triple
T32820598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-31 Hubble deployment |
E839423
|
entity |
| Predicate | telescopeOrbitAltitude |
P12741
|
FINISHED |
| Object | about 600 kilometers |
—
|
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: about 600 kilometers | Statement: [STS-31 Hubble deployment, telescopeOrbitAltitude, about 600 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeOrbitAltitude Context triple: [STS-31 Hubble deployment, telescopeOrbitAltitude, about 600 kilometers]
-
A.
orbitAltitude
chosen
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
B.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
C.
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.
-
D.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
E.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:15 a.m.