Triple

T23527601
Position Surface form Disambiguated ID Type / Status
Subject Algieba E576475 entity
Predicate hasComponent P35 FINISHED
Object Algieba 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: Algieba A | Statement: [Algieba, hasComponent, Algieba A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Algieba A
Context triple: [Algieba, hasComponent, Algieba A]
  • A. Algieba chosen
    Algieba is a bright double star system in the constellation Leo, known for its striking golden components and prominence in amateur astronomy observations.
  • B. Aghb
    Aghb is the ISO 15924 script code for the historic Caucasian Albanian writing system used by the ancient people of the eastern Caucasus.
  • C. ALGA
    ALGA is the national peak body representing local government councils across Australia, advocating their interests to the federal government and other stakeholders.
  • D. Agbaakin
    Agbaakin is a high-ranking political and advisory chief within the traditional Oyo Empire’s Oyo Mesi council in Yoruba society.
  • E. AGB
    AGB is the IATA airport code for Augsburg Airport, a regional airport serving the city of Augsburg in Bavaria, Germany.
  • 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ac74be1881909161b94aa611188a completed April 29, 2026, 7 a.m.
Created at: April 17, 2026, 6:09 p.m.