Triple
T17131560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-2B |
E415730
|
entity |
| Predicate | designedForOrbitAltitude |
P12741
|
FINISHED |
| Object | approximately 200–300 km LEO |
—
|
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 200–300 km LEO | Statement: [H-2B, designedForOrbitAltitude, approximately 200–300 km LEO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForOrbitAltitude Context triple: [H-2B, designedForOrbitAltitude, approximately 200–300 km LEO]
-
A.
designedForOrbitType
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
-
B.
orbitAltitude
chosen
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
C.
designedForOrbitInsertion
Indicates that something is intended or configured to perform or facilitate the insertion of an object into orbit.
-
D.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02a9fbc81909d820d29417aa55c |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.