Triple
T1342726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperion |
E28501
|
entity |
| Predicate | escapeVelocity_m_per_s |
P2025
|
FINISHED |
| Object | 24 |
—
|
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: 24 | Statement: [Hyperion, escapeVelocity_m_per_s, 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeVelocity_m_per_s Context triple: [Hyperion, escapeVelocity_m_per_s, 24]
-
A.
hasEscapeVelocity
chosen
Indicates that an object or body possesses a velocity sufficient to overcome the gravitational pull of another body without further propulsion.
-
B.
averageOrbitalSpeed
Indicates the typical speed at which one celestial body travels along its orbit around another over a complete orbital period.
-
C.
equatorialLinearSpeed
Indicates the linear (tangential) speed of a rotating body measured specifically at its equator.
-
D.
velocityRelativeToSun
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
-
E.
specificImpulseVac_s
Indicates the vacuum specific impulse of a propulsion system, expressing its efficiency as thrust produced per unit of propellant flow in a vacuum environment.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2174d048190a6e9380df302265f |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.