Triple
T5758874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 346 |
E127038
|
entity |
| Predicate | nebularEmission |
P24834
|
FINISHED |
| Object | H-alpha |
—
|
LITERAL 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: H-alpha | Statement: [NGC 346, nebularEmission, H-alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nebularEmission Context triple: [NGC 346, nebularEmission, H-alpha]
-
A.
isNonIonizedNebula
Indicates that the nebula is in a state where its gas is predominantly neutral rather than ionized.
-
B.
associatedNebula
chosen
Indicates a relationship where an object or entity is linked or connected to a particular nebula in some relevant way.
-
C.
notableStarburstGalaxy
Indicates that the subject is a starburst galaxy recognized as notable or significant in some context.
-
D.
hasNGCNumber
Indicates that an astronomical object is identified by a specific catalog entry in the New General Catalogue (NGC).
-
E.
galacticComponent
Indicates that one entity is a structural part or subregion of a galaxy, such as a disk, bulge, halo, or similar galactic subdivision.
- F. None of above.
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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0293771ec8190a0082685327d649b |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.