Triple
T5225877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 30 Doradus |
E117983
|
entity |
| Predicate | emitsStronglyIn |
P10551
|
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: [30 Doradus, emitsStronglyIn, H-alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emitsStronglyIn Context triple: [30 Doradus, emitsStronglyIn, H-alpha]
-
A.
occursMoreStronglyFor
Indicates that a particular effect, condition, or phenomenon manifests with greater intensity, frequency, or impact for one entity or context compared to another.
-
B.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
C.
emitted
chosen
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
D.
strongerDuring
Indicates that one entity exhibits greater strength or intensity than another specifically during a given time period or event.
-
E.
hasStrongCurrent
Indicates that one entity (typically a body of water or medium) possesses a powerful, fast-moving flow or current relative to a reference point or standard.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adc9be081909903b9f844c3d146 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.