Triple
T5362969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open cluster M16 |
E103063
|
entity |
| Predicate | messierNumber |
P20402
|
FINISHED |
| Object | M16 |
E472705
|
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: M16 | Statement: [Open cluster M16, messierNumber, M16]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M16 Context triple: [Open cluster M16, messierNumber, M16]
-
A.
M16
M16 is the Osaka Metro station code assigned to Umeda Station on the Midosuji Line in Osaka, Japan.
-
B.
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.
-
C.
M16
M16 is a Formula One racing car chassis developed and used by the Midland F1 Racing team in Grand Prix competition.
-
D.
M60
M60 is a major orbital motorway encircling the city of Manchester in Greater Manchester, England.
-
E.
M61
M61 is a major motorway in North West England connecting Manchester with Preston and linking into the wider UK motorway network.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865b9b808190a1e8c283ba28d645 |
completed | March 20, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf29205b188190a19cacbded1d5418 |
completed | March 21, 2026, 11:26 p.m. |
Created at: March 20, 2026, 2:02 p.m.