Triple
T23329422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 98087 |
E591400
|
entity |
| Predicate | isOccultedByPlanets |
P80545
|
FINISHED |
| Object | occasionally |
—
|
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: occasionally | Statement: [SAO 98087, isOccultedByPlanets, occasionally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOccultedByPlanets Context triple: [SAO 98087, isOccultedByPlanets, occasionally]
-
A.
hasBeenObservedByOccultation
Indicates that an object or phenomenon has been detected or studied through an occultation event, where it is temporarily obscured by another body.
-
B.
occultationType
chosen
Indicates the specific manner or category of an occultation event that occurs between two astronomical objects.
-
C.
canBeSeenFromEarthWith
Indicates that one entity is visible from Earth using the specified instrument, method, or observational aid.
-
D.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
E.
majorOccultationStart
Indicates the time or event at which a major occultation—when one celestial body significantly obscures another—begins.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197ec22a481908247f5f86acb6ab4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:14 p.m.