Triple
T18771416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnard 33 |
E459023
|
entity |
| Predicate | backgroundEmission |
P133478
|
FINISHED |
| Object | H-alpha emission from IC 434 |
—
|
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 emission from IC 434 | Statement: [Barnard 33, backgroundEmission, H-alpha emission from IC 434]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backgroundEmission Context triple: [Barnard 33, backgroundEmission, H-alpha emission from IC 434]
-
A.
backgroundEvent
Indicates that one event occurs in the background relative to another primary or foreground event.
-
B.
backgroundSuppression
Indicates that non-essential or contextual background elements are reduced, filtered out, or deemphasized relative to the primary subject or signal.
-
C.
laterLightSource
Indicates that one light source occurs or is activated after another in time.
-
D.
typicalBackground
Indicates that an entity has a usual or commonly expected background, context, or setting associated with it.
-
E.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.