Triple
T5060558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North America Nebula |
E114010
|
entity |
| Predicate | commonImagingBand |
P38761
|
FINISHED |
| Object | narrowband 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: narrowband H-alpha | Statement: [North America Nebula, commonImagingBand, narrowband H-alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonImagingBand Context triple: [North America Nebula, commonImagingBand, narrowband H-alpha]
-
A.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
B.
colorImaging
Indicates a relationship where an entity captures, processes, or represents visual information specifically in terms of color.
-
C.
hasSpectralChannel
chosen
Indicates that something possesses or is associated with a specific spectral channel or band within an electromagnetic spectrum.
-
D.
imageChannels
Indicates the number and types of color or data channels present in an image (e.g., RGB, RGBA, grayscale).
-
E.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.