Triple
T26412657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys Trojan moons |
E664001
|
entity |
| Predicate | areCoOrbitalWith |
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: [Tethys Trojan moons, areCoOrbitalWith, Tethys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areCoOrbitalWith Context triple: [Tethys Trojan moons, areCoOrbitalWith, Tethys]
-
A.
coOrbitsWith
chosen
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
B.
isOrbitalTo
Indicates that one entity moves in a curved, repeating path around another entity under the influence of a central force, typically gravity.
-
C.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
D.
includesOrbitOf
Indicates that one entity’s orbital path or region fully contains or encompasses the orbital path or region of another entity.
-
E.
isOrbitalRouteFor
Indicates that one path or trajectory serves as the designated orbital route followed by another object (such as a spacecraft or satellite).
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611325fd48190898639883fb113fd |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:39 p.m.