Triple
T18776041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 1295 |
E459135
|
entity |
| Predicate | hasIonizationSource |
P58484
|
FINISHED |
| Object | ultraviolet radiation from central star |
—
|
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: ultraviolet radiation from central star | Statement: [IC 1295, hasIonizationSource, ultraviolet radiation from central star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIonizationSource Context triple: [IC 1295, hasIonizationSource, ultraviolet radiation from central star]
-
A.
ionizingSource
chosen
Indicates that the subject acts as a source that produces or emits ionizing radiation affecting the object.
-
B.
hasIonizationStructure
Indicates that one entity exhibits or defines the pattern, distribution, or state of ionization present in another entity.
-
C.
hasIonizationState
Indicates the specific ionization state or charge level that an entity (such as an atom or molecule) possesses.
-
D.
hasIonizedGas
Indicates that an entity contains or is associated with gas that has been ionized (i.e., atoms or molecules with electrons removed or added).
-
E.
hasXRaySources
Indicates that an entity possesses or is associated with one or more X-ray emitting sources.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ad4288190b17e5fad57d8417d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.