Triple

T19686442
Position Surface form Disambiguated ID Type / Status
Subject Shaula E472722 entity
Predicate hasComponent P35 FINISHED
Object Shaula A NE NERFINISHED

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: Shaula A | Statement: [Shaula, hasComponent, Shaula A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shaula A
Context triple: [Shaula, hasComponent, Shaula A]
  • A. Shaula chosen
    Shaula is a bright multiple-star system marking the stinger of the constellation Scorpius and is one of the most luminous stars visible to the naked eye.
  • B. Canopus
    Canopus is the second-brightest star in the night sky, a luminous F-type supergiant prominently visible in the southern hemisphere.
  • C. Canopus
    Canopus was an ancient Egyptian coastal city near modern-day Alexandria, known as a major religious center and sanctuary dedicated to the goddess Isis.
  • D. Phecda
    Phecda is a prominent main-sequence star that forms part of the Big Dipper asterism in the constellation Ursa Major.
  • E. Carinae
    Carinae is the Latin genitive form of "Carina," commonly used in astronomy to denote stars or objects belonging to the Carina constellation.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6420c3f50819082b64b1fa4335e56 completed April 20, 2026, 3:11 p.m.
Created at: April 10, 2026, 1:45 p.m.