Triple
T26300516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn XIII |
E661541
|
entity |
| Predicate | orbitsAtSimilarDistanceAs |
P42108
|
FINISHED |
| Object | Tethys |
—
|
NE NERFINISHED |
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: Tethys | Statement: [Saturn XIII, orbitsAtSimilarDistanceAs, Tethys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsAtSimilarDistanceAs Context triple: [Saturn XIII, orbitsAtSimilarDistanceAs, Tethys]
-
A.
orbitsNear
Indicates that one object travels around another along a path that remains relatively close in spatial proximity.
-
B.
coOrbitsWith
chosen
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
C.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
D.
hasOrbitalResonanceWith
Indicates that two orbiting bodies have orbital periods in a simple integer ratio, causing their gravitational influences to repeat in a regular, synchronized pattern.
-
E.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 10:15 p.m.