Triple
T5974332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G ring |
E132946
|
entity |
| Predicate | orbitalMotion |
P58578
|
FINISHED |
| Object | prograde |
—
|
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: prograde | Statement: [G ring, orbitalMotion, prograde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalMotion Context triple: [G ring, orbitalMotion, prograde]
-
A.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
B.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
D.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
E.
hasOrbitalCharacteristic
chosen
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:03 p.m.