Triple
T36514602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAPPHIRE |
E900001
|
entity |
| Predicate | tracksAltitudeRange |
P185799
|
FINISHED |
| Object | medium Earth orbit objects |
—
|
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: medium Earth orbit objects | Statement: [SAPPHIRE, tracksAltitudeRange, medium Earth orbit objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tracksAltitudeRange Context triple: [SAPPHIRE, tracksAltitudeRange, medium Earth orbit objects]
-
A.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
altitudeRange_m
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
C.
altitudeRangeReported
Indicates that a specific range of altitudes has been reported for an entity or event, rather than a single altitude value.
-
D.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
E.
hasAltitudeDifference
Indicates that there is a specific vertical height difference between two entities or locations.
- F. None of above. chosen
Provenance (4 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.