Triple
T21424430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPS space segment |
E528516
|
entity |
| Predicate | hasOrbitalAltitude |
P12741
|
FINISHED |
| Object | about 20,200 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 20,200 kilometers | Statement: [GPS space segment, hasOrbitalAltitude, about 20,200 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalAltitude Context triple: [GPS space segment, hasOrbitalAltitude, about 20,200 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.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
C.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
reachedSuborbitalAltitude
Indicates that an object or vehicle has ascended to an altitude high enough to be considered suborbital, without achieving full orbital velocity.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813b798c8190a379cbf6cc6e14d2 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.