Triple
T1146370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn |
E23575
|
entity |
| Predicate | hasEscapeVelocity_km_per_s |
P2025
|
FINISHED |
| Object | 35.5 |
—
|
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: 35.5 | Statement: [Saturn, hasEscapeVelocity_km_per_s, 35.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEscapeVelocity_km_per_s Context triple: [Saturn, hasEscapeVelocity_km_per_s, 35.5]
-
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.
specificImpulseSeaLevel_s
Indicates the specific impulse of a propulsion system, measured in seconds, when operating at sea-level conditions.
-
D.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
E.
specificImpulseVacuum_s
Indicates the specific impulse of a propulsion system when operating in a vacuum, expressing how efficiently it converts propellant into thrust under vacuum conditions.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.