Triple
T12316042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight-Burst Nebula |
E293600
|
entity |
| Predicate | isIonizedBy |
P56979
|
FINISHED |
| Object | 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: radiation from central star | Statement: [Eight-Burst Nebula, isIonizedBy, radiation from central star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIonizedBy Context triple: [Eight-Burst Nebula, isIonizedBy, radiation from central star]
-
A.
ionizes
chosen
Indicates that one entity causes another entity to gain or lose electrons, thereby converting it into an ion.
-
B.
hasIonizationState
Indicates the specific ionization state or charge level that an entity (such as an atom or molecule) possesses.
-
C.
isElectricallyNeutral
Indicates that an entity has no net electric charge, with its positive and negative charges balanced.
-
D.
usesIonType
Indicates that one entity employs or operates using a specific type of ion in its function or process.
-
E.
hasIonTail
Indicates that an object possesses an ion tail, typically formed by ionized particles driven away by a star’s radiation or solar wind.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.