Triple

T19261787
Position Surface form Disambiguated ID Type / Status
Subject UY Scuti E481664 entity
Predicate hasStrongStellarWind P68085 FINISHED
Object yes 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: yes | Statement: [UY Scuti, hasStrongStellarWind, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStrongStellarWind
Context triple: [UY Scuti, hasStrongStellarWind, yes]
  • A. hasStellarWind chosen
    Indicates that an astronomical object emits a continuous outflow of gas or charged particles, known as a stellar wind, into the surrounding space.
  • B. hasGalacticSuperwind
    Indicates that a galaxy exhibits a large-scale, powerful outflow of gas and material driven by intense star formation or active galactic nucleus activity.
  • C. hasStellarSpectrum
    Indicates that an astronomical object exhibits a particular stellar spectrum characterizing its emitted light across wavelengths.
  • D. stellarWindTerminalVelocity
    Indicates the final, asymptotic speed reached by a star’s stellar wind far from the star, after it has been fully accelerated.
  • E. hasStellarStream
    Indicates that one astronomical object possesses or is associated with a coherent flow of stars, known as a stellar stream, typically resulting from tidal interactions or disruption.
  • 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_69d8e8ce54cc8190998418ff1f66ef28 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fb8a022c8190b313e9d11d38e482 completed April 20, 2026, 10:10 a.m.
PD Predicate disambiguation batch_69e4dd07a7208190afcd51ba1dc87c33 completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:28 p.m.