Triple
T28729913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonfly mission |
E730627
|
entity |
| Predicate | targetPlanetarySystem |
P174509
|
FINISHED |
| Object | Saturn system |
—
|
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: Saturn system | Statement: [Dragonfly mission, targetPlanetarySystem, Saturn system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPlanetarySystem Context triple: [Dragonfly mission, targetPlanetarySystem, Saturn system]
-
A.
homePlanetSystem
Indicates that one entity is the planetary system that serves as the home or origin system of the other entity.
-
B.
isInPlanetarySystem
chosen
Indicates that one celestial object is located within and belongs to a particular planetary system.
-
C.
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).
-
D.
suspectedPlanetarySystem
Indicates that an astronomical object is believed, based on available evidence, to host one or more planets but has not yet been confirmed as a planetary system.
-
E.
hasStarSystem
Indicates that an entity possesses, contains, or is associated with a particular star system.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 28, 2026, 5:58 a.m.