Triple
T32496697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn A-ring Keeler Gap |
E830543
|
entity |
| Predicate | isInPlanetarySystem |
P174509
|
FINISHED |
| Object | Saturnian system |
—
|
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: Saturnian system | Statement: [Saturn A-ring Keeler Gap, isInPlanetarySystem, Saturnian system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPlanetarySystem Context triple: [Saturn A-ring Keeler Gap, isInPlanetarySystem, Saturnian system]
-
A.
isInGalacticSystem
Indicates that one astronomical object is located within or belongs to a particular galactic system.
-
B.
isOuterSolarSystemObject
Indicates that an astronomical object resides in the outer regions of a solar system, beyond the orbit of the major inner planets.
-
C.
isPlanet
Indicates that the subject entity is classified as a planet.
-
D.
astronomicalSystem
Indicates a relationship in which multiple astronomical objects are organized into a coherent physical or dynamical system (such as a planetary system, star system, or galaxy).
-
E.
isMultipleStarSystem
Indicates that a star system contains two or more stars gravitationally bound together, rather than a single isolated star.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c41096848190aaad53c4f6255d57 |
completed | May 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:59 a.m.