Triple
T25638069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thebe |
E642759
|
entity |
| Predicate | neighboringInnerMoon |
P62574
|
FINISHED |
| Object | Amalthea |
—
|
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: Amalthea | Statement: [Thebe, neighboringInnerMoon, Amalthea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringInnerMoon Context triple: [Thebe, neighboringInnerMoon, Amalthea]
-
A.
neighboringMoon
chosen
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.
-
B.
neighboringMoons
Indicates that two moons orbiting the same or nearby celestial bodies are close enough in space to be considered neighbors.
-
C.
isOnInnermostMoonOf
Indicates that one entity is located on the innermost moon orbiting another celestial body.
-
D.
isOnLargerMoonOf
Indicates that one entity is located on a moon that is larger than another referenced moon.
-
E.
associatedMoon
Indicates that one celestial body is the moon that is associated with, or orbits, another celestial 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 5:36 p.m.