Triple

T11377035
Position Surface form Disambiguated ID Type / Status
Subject Gliese 581 star system E269494 entity
Predicate hasRadiusRelativeToSun P57022 FINISHED
Object approximately 0.29 solar radii 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: approximately 0.29 solar radii | Statement: [Gliese 581 star system, hasRadiusRelativeToSun, approximately 0.29 solar radii]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRadiusRelativeToSun
Context triple: [Gliese 581 star system, hasRadiusRelativeToSun, approximately 0.29 solar radii]
  • A. hasRadius_solarRadius chosen
    Indicates that an entity has a radius whose value is expressed in units of the Sun’s radius.
  • B. approximateDistanceFromSun
    Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
  • C. hasMeanDistanceFromSun
    Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
  • D. hasMeanRadius
    Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
  • E. radiusRelativeToJupiter
    Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d800160a1c81909d115bf89fe54a49 completed April 9, 2026, 7:37 p.m.
PD Predicate disambiguation batch_69d7e7022d508190996f9be0847c2b41 completed April 9, 2026, 5:50 p.m.
Created at: April 8, 2026, 9:33 p.m.