Triple

T6246305
Position Surface form Disambiguated ID Type / Status
Subject Messier 44 E139728 entity
Predicate hasTidalRadius P56976 FINISHED
Object about 39 light-years 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: about 39 light-years | Statement: [Messier 44, hasTidalRadius, about 39 light-years]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTidalRadius
Context triple: [Messier 44, hasTidalRadius, about 39 light-years]
  • A. tidalRadius_pc chosen
    Indicates the radius, measured in parsecs, within which an object (such as a star cluster or satellite) remains gravitationally bound before external tidal forces dominate.
  • B. isTidalInteractionSuspected
    Indicates that a gravitational interaction between astronomical bodies is suspected to be causing observable tidal effects or disturbances.
  • C. hasMeanRadius
    Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
  • D. isTidal
    Indicates that something is influenced or driven by tidal forces or tidal movements.
  • E. isBeingTidallyDisruptedBy
    Indicates that one astronomical object is currently being torn apart or significantly deformed by the tidal gravitational forces of another object.
  • 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_69c008b1c5088190ae6de2555fc05ad8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0631d9e648190a59ab4001f506424 completed March 22, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69c056037bf88190a0a3fe7429345d0b completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:23 p.m.