Triple
T13256725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEO |
E315677
|
entity |
| Predicate | typicalPerigeeAltitudeUpperBound_km |
P26358
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [LEO, typicalPerigeeAltitudeUpperBound_km, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerigeeAltitudeUpperBound_km Context triple: [LEO, typicalPerigeeAltitudeUpperBound_km, 2000]
-
A.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
B.
perigee
chosen
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
C.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
minimumOrbitIntersectionDistanceWithEarth_au
Indicates the smallest distance, measured in astronomical units, between an object's orbit and Earth's orbit at their closest point of approach.
-
E.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.