Triple
T33840225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble gyroscopes |
E867338
|
entity |
| Predicate | orbitEnvironment |
P7214
|
FINISHED |
| Object | low Earth orbit around Earth |
—
|
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: low Earth orbit around Earth | Statement: [Hubble gyroscopes, orbitEnvironment, low Earth orbit around Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitEnvironment Context triple: [Hubble gyroscopes, orbitEnvironment, low Earth orbit around Earth]
-
A.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
orbitsEarth
Indicates that one object follows a gravitationally bound path around Earth as its primary central body.
-
C.
orbitShape
Indicates the geometric form or path pattern that an orbiting object follows around another body.
-
D.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
E.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.