Triple
T5509109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dione |
E144515
|
entity |
| Predicate | relativePositionAmongMajorMoons |
P65151
|
FINISHED |
| Object | orbits outside Enceladus |
—
|
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: orbits outside Enceladus | Statement: [Dione, relativePositionAmongMajorMoons, orbits outside Enceladus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionAmongMajorMoons Context triple: [Dione, relativePositionAmongMajorMoons, orbits outside Enceladus]
-
A.
rankBySizeAmongMoons
Indicates the ordinal position of a moon in a size-based ranking relative to other moons.
-
B.
neighboringMoons
Indicates that two moons orbiting the same or nearby celestial bodies are close enough in space to be considered neighbors.
-
C.
areLargestMoonsOf
Indicates that the referenced moons are the largest natural satellites belonging to the specified celestial bodies.
-
D.
neighboringMoon
Indicates that one moon or natural satellite is directly adjacent to or in close orbital proximity to another moon around the same or nearby celestial body.
-
E.
numberOfKnownMoons
Indicates the count of moons that are currently known to orbit a given celestial body.
- F. None of above. chosen
Provenance (4 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4a80d88190bab0056c4c78be93 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:33 p.m.