Triple
T4531482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosette Nebula |
E106307
|
entity |
| Predicate | dominantEmissionLine |
P41863
|
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: [Rosette Nebula, dominantEmissionLine, H-alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantEmissionLine Context triple: [Rosette Nebula, dominantEmissionLine, H-alpha]
-
A.
dominantEmissionLines
chosen
Indicates that the specified emission lines are the most intense or prominent spectral features in the observed emission from an object or region.
-
B.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
C.
dominantExcitationSource
Indicates that one entity serves as the primary or most influential source of excitation affecting another entity or system.
-
D.
primaryWavelength
Indicates the main or dominant wavelength associated with an entity, such as the principal wavelength at which it emits, reflects, or operates.
-
E.
dominantProcess
Indicates that one process exerts primary control or influence over another process within a given context.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.