Triple
T25677226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sark |
E643840
|
entity |
| Predicate | darkSkyStatusYear |
P84243
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Sark, darkSkyStatusYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: darkSkyStatusYear Context triple: [Sark, darkSkyStatusYear, 2011]
-
A.
darkSkyStatusGrantedBy
Indicates that a particular dark sky status or designation has been officially conferred by a specified granting authority or organization.
-
B.
darkSkyRecognition
chosen
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.
-
C.
allWeatherCapability
Indicates that an entity is capable of operating effectively under all weather conditions.
-
D.
skyBeamVisibility
Indicates that a skyward-directed beam (such as a light or energy beam) is visible from a given location or viewpoint.
-
E.
meteorologicalStatus
Indicates the current or historical weather-related condition or state affecting an entity or location.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3712cc8190b6e851960cc7c9e9 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:40 p.m.