Triple
T11000534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun-synchronous orbit |
E259991
|
entity |
| Predicate | hasTypicalAltitude |
P50137
|
FINISHED |
| Object | approximately 600 to 800 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: approximately 600 to 800 kilometers | Statement: [Sun-synchronous orbit, hasTypicalAltitude, approximately 600 to 800 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAltitude Context triple: [Sun-synchronous orbit, hasTypicalAltitude, approximately 600 to 800 kilometers]
-
A.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
hasAltitudeFeature
chosen
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
C.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
D.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
E.
visibilityAltitude
Indicates the altitude at which something becomes visible or can be seen.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d68b608190a8d016b9383e82f8 |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.