Triple

T9516157
Position Surface form Disambiguated ID Type / Status
Subject Vera Rubin Ridge E229529 entity
Predicate hasOrbitalSignature P88500 FINISHED
Object strong hematite spectral absorption 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: strong hematite spectral absorption | Statement: [Vera Rubin Ridge, hasOrbitalSignature, strong hematite spectral absorption]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrbitalSignature
Context triple: [Vera Rubin Ridge, hasOrbitalSignature, strong hematite spectral absorption]
  • A. hasOrbitalCharacteristic
    Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
  • B. hasOrbitalRegion
    Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
  • C. hasOrbitalStability
    Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
  • D. hasOrbitalPlane
    Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
  • E. isOnOrbital
    Indicates that one entity is located on or traveling along the orbital path associated with 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_69ca84777560819084cddd999badc1aa completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd987eefec8190b0db1928776bf02b completed April 1, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69cca56a3d088190bdc16670678fb6c6 completed April 1, 2026, 4:56 a.m.
PDg Predicate description generation batch_69cca89d0f0c8190b4528990fe708fca completed April 1, 2026, 5:09 a.m.
Created at: March 30, 2026, 7:58 p.m.