Triple
T20479233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verona Rupes |
E502405
|
entity |
| Predicate | hostBodyOrbits |
P110320
|
FINISHED |
| Object | Uranus in a prograde, inclined orbit |
—
|
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: Uranus in a prograde, inclined orbit | Statement: [Verona Rupes, hostBodyOrbits, Uranus in a prograde, inclined orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostBodyOrbits Context triple: [Verona Rupes, hostBodyOrbits, Uranus in a prograde, inclined orbit]
-
A.
hostOrbit
chosen
Indicates that one celestial body orbits around another body that serves as its primary gravitational host.
-
B.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
C.
orbitsPrimaryViaHostBody
Indicates that an object orbits its primary body indirectly by orbiting an intermediate host body which itself orbits that primary.
-
D.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
E.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b54c8188190a71e35fab8d194a6 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.