Triple

T5259745
Position Surface form Disambiguated ID Type / Status
Subject Naiad E118793 entity
Predicate orbitalConfiguration P7214 FINISHED
Object closely packed inner satellite 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: closely packed inner satellite system | Statement: [Naiad, orbitalConfiguration, closely packed inner satellite system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orbitalConfiguration
Context triple: [Naiad, orbitalConfiguration, closely packed inner satellite system]
  • A. hasElectronConfiguration
    Indicates that an entity (typically an atom or ion) possesses a specific arrangement of electrons in its atomic orbitals.
  • B. hasOrbitalStability
    Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
  • C. BohrPosition
    Indicates the specific orbit or energy level an electron occupies around an atomic nucleus according to the Bohr model.
  • D. hasOrbitalCharacteristic
    Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
  • E. orbitType chosen
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • 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_69bd446a42c88190b7ecbef006561d55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7bcced6881909bdb7ac5471a37fe completed March 20, 2026, 4:54 p.m.
PD Predicate disambiguation batch_69bd77c55224819096c0bcfcfae79bd3 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:50 p.m.