Triple

T18956402
Position Surface form Disambiguated ID Type / Status
Subject NGC 2023 E463790 entity
Predicate catalogCode P8090 FINISHED
Object NGC 2023 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: NGC 2023 | Statement: [NGC 2023, catalogCode, NGC 2023]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NGC 2023
Context triple: [NGC 2023, catalogCode, NGC 2023]
  • A. NGC 2023 chosen
    NGC 2023 is a bright reflection nebula in the constellation Orion, illuminated by a young B-type star and noted for its complex dust and gas structures.
  • B. 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.
  • C. NGC 2032
    NGC 2032 is a bright emission nebula and star-forming region located in the Large Magellanic Cloud within the constellation Dorado.
  • D. NGC 2004
    NGC 2004 is a rich young star cluster located in the Large Magellanic Cloud within the southern constellation Dorado.
  • E. NGC 2070
    NGC 2070 is a massive, luminous star-forming region in the Large Magellanic Cloud, best known for containing the dense star cluster R136 and powering the Tarantula 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