Triple

T18956320
Position Surface form Disambiguated ID Type / Status
Subject Vela E463788 entity
Predicate contains P35 FINISHED
Object NGC2547 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: NGC2547 | Statement: [Vela, contains, NGC2547]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NGC2547
Context triple: [Vela, contains, NGC2547]
  • A. NGC2547 chosen
    NGC 2547 is a young open star cluster located in the constellation Vela, notable for its bright, hot stars and relatively close distance to Earth.
  • B. NGC 2345
    NGC 2345 is an open star cluster located in the constellation Monoceros, notable for its young, massive stars and rich stellar population.
  • C. NGC 2343
    NGC 2343 is an open star cluster located in the constellation Monoceros.
  • D. NGC 2251
    NGC 2251 is an open star cluster located in the constellation Monoceros, observed as a loose grouping of stars within the Milky Way.
  • E. NGC 2024
    NGC 2024, also known as the Flame Nebula, is a bright emission nebula and active star-forming region located in the constellation Orion near the Horsehead Nebula.
  • 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5cdf2d08190a0aecd3fa5335a75 completed April 20, 2026, 7:29 a.m.
Created at: April 10, 2026, noon