Triple
T33797013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium LLC |
E866100
|
entity |
| Predicate | satelliteOrbitAltitude |
P12741
|
FINISHED |
| Object | low Earth orbit |
—
|
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 | Statement: [Iridium LLC, satelliteOrbitAltitude, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satelliteOrbitAltitude Context triple: [Iridium LLC, satelliteOrbitAltitude, low Earth orbit]
-
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.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
C.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
E.
KármánLineAltitude
Indicates that the specified altitude corresponds to the Kármán line, the conventional boundary between Earth's atmosphere and outer space.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.