Triple

T19685706
Position Surface form Disambiguated ID Type / Status
Subject M16 E472705 entity
Predicate messierNumber P20402 FINISHED
Object M16 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: M16 | Statement: [M16, messierNumber, M16]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M16
Context triple: [M16, messierNumber, M16]
  • A. M16 chosen
    M16, also known as the Eagle Nebula, is a famous star-forming region in the constellation Serpens, best known for the "Pillars of Creation" captured by the Hubble Space Telescope.
  • B. M16
    M16 is the Osaka Metro station code assigned to Umeda Station on the Midosuji Line in Osaka, Japan.
  • C. M16
    M16 is a Formula One racing car chassis developed and used by the Midland F1 Racing team in Grand Prix competition.
  • D. M14
    M14 is a globular star cluster in the constellation Ophiuchus, notable for its dense concentration of ancient stars and inclusion in the Messier catalog.
  • E. M19
    M19 is a globular star cluster in the constellation Ophiuchus, notable for its high ellipticity and inclusion in Charles Messier’s catalog of deep-sky objects.
  • 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e641c33b94819081bdeb56910f6ff8 completed April 20, 2026, 3:09 p.m.
Created at: April 10, 2026, 1:45 p.m.