Triple
T3687713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alta |
E78263
|
entity |
| Predicate | hasAuroraObservations |
P34853
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Alta, hasAuroraObservations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuroraObservations Context triple: [Alta, hasAuroraObservations, yes]
-
A.
hasNearbyObservatories
Indicates that one entity has one or more observatories located in close geographic proximity to it.
-
B.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
C.
containsAstronomicalEvent
chosen
Indicates that a location, region, or time period includes or encompasses a specific astronomical event within its bounds or duration.
-
D.
hasBeenObservedByOccultation
Indicates that an object or phenomenon has been detected or studied through an occultation event, where it is temporarily obscured by another body.
-
E.
visibleToNakedEye
Indicates that something can be perceived directly without the aid of optical instruments such as telescopes, microscopes, or binoculars.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c7e2bc81909356c8b0ed90feed |
completed | March 8, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.