Triple
T30863260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSMIC-1 constellation |
E786120
|
entity |
| Predicate | orbitAltitudeApprox |
P12741
|
FINISHED |
| Object | 800 km |
—
|
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: 800 km | Statement: [COSMIC-1 constellation, orbitAltitudeApprox, 800 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitAltitudeApprox Context triple: [COSMIC-1 constellation, orbitAltitudeApprox, 800 km]
-
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.
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.
-
C.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
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.
-
E.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:47 p.m.