Triple
T11658733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nether |
E277070
|
entity |
| Predicate | skyVisibility |
P349
|
FINISHED |
| Object | no sky |
—
|
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: no sky | Statement: [Nether, skyVisibility, no sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyVisibility Context triple: [Nether, skyVisibility, no sky]
-
A.
skyBeamVisibility
Indicates that a skyward-directed beam (such as a light or energy beam) is visible from a given location or viewpoint.
-
B.
skyQuality
chosen
Indicates the measured level or condition of the sky, typically in terms of clarity, brightness, or suitability for observation.
-
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.
darkSkyStatusGrantedBy
Indicates that a particular dark sky status or designation has been officially conferred by a specified granting authority or organization.
-
E.
skyConditionAdvantage
Indicates that certain sky or weather conditions provide a beneficial effect or favorable advantage to an entity or activity.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.