Triple
T11993945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroccan Sahara |
E285479
|
entity |
| Predicate | nightSky |
P349
|
FINISHED |
| Object | low light pollution |
—
|
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: low light pollution | Statement: [Moroccan Sahara, nightSky, low light pollution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nightSky Context triple: [Moroccan Sahara, nightSky, low light pollution]
-
A.
skyQuality
chosen
Indicates the measured level or condition of the sky, typically in terms of clarity, brightness, or suitability for observation.
-
B.
visibleInEveningSky
Indicates that the entity can be seen in the sky during evening hours.
-
C.
darkSkyRecognition
Indicates formal recognition that a location meets specific criteria for dark sky quality, such as minimal light pollution and suitability for stargazing or astronomical observation.
-
D.
rankByBrightnessInNightSky
Indicates the relative ordering of celestial objects based on how bright they appear in the night sky.
-
E.
meteorBrightness
Indicates the observed luminous intensity or apparent brightness of a meteor during its visible passage.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903b211688190bfe6dd15c3f96d2f |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.