Triple

T992636
Position Surface form Disambiguated ID Type / Status
Subject Sagittarius Dwarf Spheroidal Galaxy E21424 entity
Predicate orbitalPlane P7296 FINISHED
Object nearly polar orbit around Milky Way 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: nearly polar orbit around Milky Way | Statement: [Sagittarius Dwarf Spheroidal Galaxy, orbitalPlane, nearly polar orbit around Milky Way]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orbitalPlane
Context triple: [Sagittarius Dwarf Spheroidal Galaxy, orbitalPlane, nearly polar orbit around Milky Way]
  • A. hasOrbitalPlane chosen
    Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
  • B. orbitType
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • C. orbitedBody
    Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
  • D. ringPlane
    Indicates that one entity lies within or corresponds to the geometric plane defined by a ring structure associated with another entity.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4c3f7b48190a31308bdc09817c6 completed March 1, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69a4b2adbde48190b07966d0c3179516 completed March 1, 2026, 9:42 p.m.
Created at: March 1, 2026, 7:41 p.m.