Triple

T21163864
Position Surface form Disambiguated ID Type / Status
Subject Local Group E521507 entity
Predicate contains P35 FINISHED
Object Andromeda XIII 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: Andromeda XIII | Statement: [Local Group, contains, Andromeda XIII]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andromeda XIII
Context triple: [Local Group, contains, Andromeda XIII]
  • A. Andromeda XIII chosen
    Andromeda XIII is a faint dwarf spheroidal satellite galaxy of the Andromeda Galaxy located within the Local Group.
  • B. Andromeda III
    Andromeda III is a dwarf spheroidal satellite galaxy of the Andromeda Galaxy located within the Local Group.
  • C. Andromeda XXII
    Andromeda XXII is a faint dwarf satellite galaxy located near the Andromeda Galaxy within the Local Group of galaxies.
  • D. Andromeda XVI
    Andromeda XVI is a faint dwarf spheroidal satellite galaxy of the Andromeda Galaxy located within the Local Group.
  • E. Andromeda VIII
    Andromeda VIII is a faint dwarf satellite galaxy of the Andromeda Galaxy (M31), believed to be part of its extended galactic system in the Local Group.
  • 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_69e0b50d1ea481909c07e63c3ead9316 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72533fe88819082e14d71c36140be completed April 21, 2026, 7:20 a.m.
Created at: April 16, 2026, 2:59 p.m.