Triple
T5958650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betelgeuse |
E132578
|
entity |
| Predicate | hasObservedDimmingEvent |
P26705
|
FINISHED |
| Object | 2019–2020 great dimming |
—
|
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: 2019–2020 great dimming | Statement: [Betelgeuse, hasObservedDimmingEvent, 2019–2020 great dimming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservedDimmingEvent Context triple: [Betelgeuse, hasObservedDimmingEvent, 2019–2020 great dimming]
-
A.
hasObservation
chosen
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
B.
hasBeenObservedByOccultation
Indicates that an object or phenomenon has been detected or studied through an occultation event, where it is temporarily obscured by another body.
-
C.
hasObserver
Indicates that an entity is being watched, monitored, or examined by another entity acting as an observer.
-
D.
isIlluminatedAtNight
Indicates that an entity receives or emits sufficient light to be visibly illuminated during nighttime conditions.
-
E.
hasObserverStatusAt
Indicates that an entity holds observer status or role at a specified organization, event, or 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.