Triple
T18956362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flame Nebula |
E463789
|
entity |
| Predicate | ionizingSourceType |
P58484
|
FINISHED |
| Object | massive O-type 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: massive O-type star | Statement: [Flame Nebula, ionizingSourceType, massive O-type star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ionizingSourceType Context triple: [Flame Nebula, ionizingSourceType, massive O-type star]
-
A.
ionizingSource
chosen
Indicates that the subject acts as a source that produces or emits ionizing radiation affecting the object.
-
B.
radiatedFrom
Indicates that something (such as energy, particles, or influence) originates at a source and spreads outward from that source.
-
C.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
D.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
-
E.
neutronFluxType
Indicates the specific classification or category of neutron flux characterizing how neutrons are distributed or behave in 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cdf2d08190a0aecd3fa5335a75 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon