Triple

T29581114
Position Surface form Disambiguated ID Type / Status
Subject Ganymede stories by Gregory Benford E753585 entity
Predicate celestialBodyFeatured P167465 FINISHED
Object Jupiter 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: Jupiter | Statement: [Ganymede stories by Gregory Benford, celestialBodyFeatured, Jupiter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: celestialBodyFeatured
Context triple: [Ganymede stories by Gregory Benford, celestialBodyFeatured, Jupiter]
  • A. observedAstronomicalBody
    Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
  • B. cosmicBodies
    Indicates a relationship in which entities are identified as astronomical or celestial objects existing in outer space.
  • C. hasAstronomicalFeature
    Indicates that an entity possesses, contains, or is characterized by a specific astronomical feature (such as a star, planet, crater, or other celestial structure).
  • D. majorBody
    Indicates that one entity is the primary or most significant body (e.g., celestial, organizational, or governing body) in relation to another entity.
  • E. astronomicalCharacteristic
    Indicates that one entity has a specific astronomical property, feature, or attribute in relation to another entity.
  • 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_69f0ef80bf8c8190ad286e99f7df0c63 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66d7a4460819092b22b56609cc7ed completed May 2, 2026, 9:32 p.m.
PD Predicate disambiguation batch_69f6659d36208190b01412600a4ed57d completed May 2, 2026, 8:59 p.m.
PDg Predicate description generation batch_69f6691da93081909deaf680614fc900 completed May 2, 2026, 9:14 p.m.
Created at: April 28, 2026, 6:07 p.m.