Triple
T19575482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacman Nebula |
E489843
|
entity |
| Predicate | catalogNumber |
P8090
|
FINISHED |
| Object | NGC 281 |
—
|
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 281 | Statement: [Pacman Nebula, catalogNumber, NGC 281]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NGC 281 Context triple: [Pacman Nebula, catalogNumber, NGC 281]
-
A.
NGC 281
chosen
NGC 281 is an emission nebula in the constellation Cassiopeia, notable for its active star formation regions and distinctive shape that inspired the nickname "Pacman Nebula."
-
B.
NGC 2841
NGC 2841 is a massive, relatively nearby spiral galaxy notable for its tightly wound arms, low star formation rate, and prominent dust lanes.
-
C.
NGC 5822
NGC 5822 is an open star cluster located in the southern constellation Lupus.
-
D.
NGC 221
NGC 221 is a compact dwarf elliptical galaxy in the Local Group, best known as the bright satellite galaxy M32 orbiting the Andromeda Galaxy.
-
E.
NGC2899
NGC 2899 is a bright, butterfly-shaped planetary nebula located in the constellation Vela.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64023fe148190900c6887896c8ea0 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.