Triple

T18458087
Position Surface form Disambiguated ID Type / Status
Subject Monoceros OB2 association E450956 entity
Predicate contains P35 FINISHED
Object NGC 2244 E554483 NE FINISHED

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 2244 | Statement: [Monoceros OB2 association, contains, NGC 2244]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NGC 2244
Context triple: [Monoceros OB2 association, contains, NGC 2244]
  • A. NGC 2244 chosen
    NGC 2244 is a young open star cluster embedded in the Rosette Nebula, located in the constellation Monoceros.
  • B. NGC 2254
    NGC 2254 is an open star cluster located in the constellation Monoceros.
  • C. NGC 2239
    NGC 2239 is an open star cluster located in the constellation Monoceros, often associated with the Rosette Nebula region.
  • D. 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.
  • E. NGC 2345
    NGC 2345 is an open star cluster located in the constellation Monoceros, notable for its young, massive stars and rich stellar population.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e52a7c18d88190ac17f58111722223 completed April 19, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a05036c7b8c8190a6baa54636f8e705 completed May 13, 2026, 11:04 p.m.
Created at: April 10, 2026, 11:31 a.m.