Triple
T22228505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsilon Orionis |
E549405
|
entity |
| Predicate | emitsStrong |
P10551
|
FINISHED |
| Object | ultraviolet radiation |
—
|
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 | Statement: [Epsilon Orionis, emitsStrong, ultraviolet radiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emitsStrong Context triple: [Epsilon Orionis, emitsStrong, ultraviolet radiation]
-
A.
emitted
chosen
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
B.
occursMoreStronglyFor
Indicates that a particular effect, condition, or phenomenon manifests with greater intensity, frequency, or impact for one entity or context compared to another.
-
C.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
D.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
-
E.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf0a03c8190ac4717cce902b2cd |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.