Triple

T21163837
Position Surface form Disambiguated ID Type / Status
Subject Local Group E521507 entity
Predicate contains P35 FINISHED
Object IC 10 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: IC 10 | Statement: [Local Group, contains, IC 10]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IC 10
Context triple: [Local Group, contains, IC 10]
  • A. IC 10 chosen
    IC 10 is a nearby irregular starburst galaxy notable for its intense star formation and membership in the Local Group.
  • B. IC 1795
    IC 1795 is a bright star-forming nebula in the constellation Cassiopeia, located near the Heart Nebula (IC 1805) within the Perseus Arm of the Milky Way.
  • C. IC 1295
    IC 1295 is a faint planetary nebula located in the constellation Scutum, notable for its roughly circular shell of ionized gas surrounding a central white dwarf.
  • D. IC 4970
    IC 4970 is a lenticular companion galaxy interacting gravitationally with the large spiral galaxy NGC 6872 in the constellation Pavo.
  • E. IC 4812
    IC 4812 is a reflection nebula located in the constellation Corona Australis, associated with a region of active star formation.
  • 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.