Triple
T13353046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 2 |
E318115
|
entity |
| Predicate | suborbitalRange |
P109048
|
FINISHED |
| Object | approximately 3,400 kilometers |
—
|
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 3,400 kilometers | Statement: [Gemini 2, suborbitalRange, approximately 3,400 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suborbitalRange Context triple: [Gemini 2, suborbitalRange, approximately 3,400 kilometers]
-
A.
reachedSuborbitalAltitude
Indicates that an object or vehicle has ascended to an altitude high enough to be considered suborbital, without achieving full orbital velocity.
-
B.
rocketCaliber
Indicates the diameter or size classification of a rocket, typically specifying the width of its body or projectile.
-
C.
firstSuborbitalFlightDate
Indicates the calendar date on which an entity’s first suborbital flight occurred.
-
D.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
E.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8d520881908aa23c7102b72b72 |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d9903fc2248190bd9894a45a2d0359 |
completed | April 11, 2026, 12:05 a.m. |
Created at: April 9, 2026, 9:32 p.m.