Triple
T38070647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega Beams |
E950580
|
entity |
| Predicate | emissionPoint |
P51025
|
FINISHED |
| Object | Darkseid's eyes |
—
|
NE NERFINISHED |
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: Darkseid's eyes | Statement: [Omega Beams, emissionPoint, Darkseid's eyes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionPoint Context triple: [Omega Beams, emissionPoint, Darkseid's eyes]
-
A.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
-
B.
pointSource
chosen
Indicates that an entity acts as a localized origin or emitter of some quantity (such as light, sound, or radiation) concentrated at a single point in space.
-
C.
emissionCharacteristic
Indicates a relationship where an entity is associated with a specific property or quality of its emissions (such as type, level, or pattern of emission).
-
D.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
E.
emergesAt
Indicates that something comes into existence, becomes visible, or starts to be apparent at a specific time, place, or condition.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.