Triple

T30067668
Position Surface form Disambiguated ID Type / Status
Subject Arago (Martian crater) E764078 entity
Predicate locatedInPlanetarySystem P174509 FINISHED
Object Solar 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: Solar System | Statement: [Arago (Martian crater), locatedInPlanetarySystem, Solar System]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInPlanetarySystem
Context triple: [Arago (Martian crater), locatedInPlanetarySystem, Solar System]
  • A. isInPlanetarySystem chosen
    Indicates that one celestial object is located within and belongs to a particular planetary system.
  • B. hasStarSystem
    Indicates that an entity possesses, contains, or is associated with a particular star system.
  • C. 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.
  • D. isOuterSolarSystemObject
    Indicates that an astronomical object resides in the outer regions of a solar system, beyond the orbit of the major inner planets.
  • E. systemHasInnerAsteroidBelt
    Indicates that a planetary system contains an asteroid belt located in its inner region, closer to the central star than any outer belts.
  • 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_69f2247221388190a13a22c47094a0ef completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a009a0e1fa481909ed881012009b268 completed May 10, 2026, 2:45 p.m.
PD Predicate disambiguation batch_6a0092e9fcb08190a966d720684f25ec completed May 10, 2026, 2:15 p.m.
Created at: April 29, 2026, 7 p.m.