Triple

T6457863
Position Surface form Disambiguated ID Type / Status
Subject HR 1156 E142037 entity
Predicate hasVariableStarStatus P69917 FINISHED
Object not known to be variable 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: not known to be variable | Statement: [HR 1156, hasVariableStarStatus, not known to be variable]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVariableStarStatus
Context triple: [HR 1156, hasVariableStarStatus, not known to be variable]
  • A. hasVariableStarDesignation
    Indicates that an entity is assigned a specific variable star designation in an astronomical naming system.
  • B. isVariableStar
    Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
  • C. isSuspectedVariableStar chosen
    Indicates that an astronomical object is believed, based on preliminary or incomplete evidence, to exhibit variability in its brightness over time but has not yet been confirmed as a variable star.
  • D. variableStarType
    Indicates the specific classification of variability that characterizes a variable star’s changing brightness.
  • E. hasStellarSpectrum
    Indicates that an astronomical object exhibits a particular stellar spectrum characterizing its emitted light across wavelengths.
  • 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_69c008d2f91c8190a8178767a35e08fc completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c069d758508190b9c7358ef84f8169 completed March 22, 2026, 10:14 p.m.
PD Predicate disambiguation batch_69c0673b44148190aed70084f0ff4992 completed March 22, 2026, 10:03 p.m.
Created at: March 22, 2026, 4:48 p.m.