Triple
T25639017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herse |
E642784
|
entity |
| Predicate | orbitalGroup |
P111182
|
FINISHED |
| Object | distant retrograde group of Jupiter moons |
—
|
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: distant retrograde group of Jupiter moons | Statement: [Herse, orbitalGroup, distant retrograde group of Jupiter moons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalGroup Context triple: [Herse, orbitalGroup, distant retrograde group of Jupiter moons]
-
A.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
B.
hasOrbitalFamily
chosen
Indicates that one celestial body belongs to the same group or class of objects that share similar orbital characteristics with another.
-
C.
orbitalComponent
Indicates that one entity is a component or part of another entity’s orbital system or orbital structure.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another 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_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 5:38 p.m.