Triple

T10672268
Position Surface form Disambiguated ID Type / Status
Subject 1762 Russell E251517 entity
Predicate namedForKnownFor P95239 FINISHED
Object stellar classification 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: stellar classification | Statement: [1762 Russell, namedForKnownFor, stellar classification]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: namedForKnownFor
Context triple: [1762 Russell, namedForKnownFor, stellar classification]
  • A. laterKnownFor
    Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
  • B. alsoKnownFor
    Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
  • C. underlyingKnownFor
    Indicates that one entity is fundamentally or primarily recognized as the basis or main reason for another entity’s notability or fame.
  • D. formerlyKnownFor
    Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
  • E. creatorKnownFor
    Indicates that a creator is especially recognized or notable for a particular work, contribution, or achievement.
  • F. None of above. chosen

Provenance (4 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_69d6aa5b0d2881909584b20efc5877f0 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6f8659d40819087a2709bd24261ee completed April 9, 2026, 12:52 a.m.
PD Predicate disambiguation batch_69d6dd8a93208190a573061387e2aebb completed April 8, 2026, 10:58 p.m.
PDg Predicate description generation batch_69d6df47899481909ac0e518d94883cb completed April 8, 2026, 11:05 p.m.
Created at: April 8, 2026, 9:09 p.m.