Triple
T25643011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Shepard booster |
E642881
|
entity |
| Predicate | flightProfileApogee |
P52278
|
FINISHED |
| Object | over 100 kilometers altitude |
—
|
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: over 100 kilometers altitude | Statement: [New Shepard booster, flightProfileApogee, over 100 kilometers altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightProfileApogee Context triple: [New Shepard booster, flightProfileApogee, over 100 kilometers altitude]
-
A.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
B.
firstSpaceflightApogee
Indicates the maximum altitude above a celestial body that an entity reached during its first spaceflight.
-
C.
reachedApogee
Indicates that an object in orbit has arrived at the highest point (apogee) in its trajectory around a central body.
-
D.
reachedSuborbitalAltitude
chosen
Indicates that an object or vehicle has ascended to an altitude high enough to be considered suborbital, without achieving full orbital velocity.
-
E.
highestAltitudeReachedBy
Indicates the maximum altitude that a given entity has ever attained.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa22e7c81908af7fe96952bebe0 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 5:46 p.m.