Triple

T23527682
Position Surface form Disambiguated ID Type / Status
Subject HR 3429 E576476 entity
Predicate hasRoleInAstronomy P45576 FINISHED
Object usedAsReferenceStarInCancer 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: usedAsReferenceStarInCancer | Statement: [HR 3429, hasRoleInAstronomy, usedAsReferenceStarInCancer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoleInAstronomy
Context triple: [HR 3429, hasRoleInAstronomy, usedAsReferenceStarInCancer]
  • A. astronomicalRole chosen
    Indicates the functional or positional role that one astronomical object or entity has in relation to another (e.g., star vs. planet, primary vs. satellite).
  • B. roleInAstrophysics
    Indicates that an entity holds a specific professional, academic, or functional role within the field of astrophysics.
  • C. isLinkedToAstronomy
    Indicates that something has a connection or relevant association to the field or study of astronomy.
  • D. astronomicalIdentity
    Indicates that two astronomical entities are in fact the same object or refer to the same celestial body, despite possibly having different names or identifiers.
  • E. telescopeRole
    Indicates the functional role or purpose that a telescope serves within an observation, system, or activity.
  • 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ac74be1881909161b94aa611188a completed April 29, 2026, 7 a.m.
PD Predicate disambiguation batch_69f1189d75b48190a1c01928a993c9fb completed April 28, 2026, 8:29 p.m.
Created at: April 17, 2026, 6:09 p.m.