Triple

T18842443
Position Surface form Disambiguated ID Type / Status
Subject ξ Persei E460829 entity
Predicate stellarWind P68085 FINISHED
Object strong 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: strong | Statement: [ξ Persei, stellarWind, strong]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stellarWind
Context triple: [ξ Persei, stellarWind, strong]
  • 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. stellarEnvironment
    Indicates the surrounding physical and spatial conditions associated with a star, such as its nearby matter, radiation fields, and local cosmic environment.
  • C. stellarClass
    Indicates the spectral classification relationship between a star and its stellar class (e.g., O, B, A, F, G, K, M).
  • D. starSystem
    Indicates a relationship where an astronomical object or location belongs to, is part of, or is located within a particular star system.
  • E. stellarMass
    Indicates the amount of mass an astronomical object has that is contained in its stars.
  • 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_69d8dcfa11e4819090ab1ef5bdcd2b2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5b8eb32548190b2313e877f6ff179 completed April 20, 2026, 5:26 a.m.
PD Predicate disambiguation batch_69e48d1e7dac81909ea1e758c87773c5 completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:56 a.m.