Triple

T869986
Position Surface form Disambiguated ID Type / Status
Subject Seven Sisters E18787 entity
Predicate hasProperMotion P6962 FINISHED
Object common cluster motion 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: common cluster motion | Statement: [Seven Sisters, hasProperMotion, common cluster motion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProperMotion
Context triple: [Seven Sisters, hasProperMotion, common cluster motion]
  • A. properMotion chosen
    Indicates the apparent angular movement of an astronomical object across the sky relative to distant background objects over time.
  • B. apparentMagnitude
    Indicates the observed brightness of an astronomical object as seen from Earth, on a logarithmic scale where lower values correspond to brighter appearances.
  • C. astronomicalCharacteristic
    Indicates that one entity has a specific astronomical property, feature, or attribute in relation to another entity.
  • D. hasMeanDistanceFromSun
    Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
  • E. hasOrbitalPeriod
    Indicates that one entity completes a full orbit around another entity within a specified duration.
  • 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_69a4938ce8688190a24bdfef82ba7d21 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac811e548190a72b7a10b5ea8665 completed March 1, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69a4aa89ca008190b50d061ac7fe19f9 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.