Triple
T21512246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWh |
E530754
|
entity |
| Predicate | hasCloudCoverCharacteristic |
P26038
|
FINISHED |
| Object | low annual cloudiness |
—
|
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 annual cloudiness | Statement: [BWh, hasCloudCoverCharacteristic, low annual cloudiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloudCoverCharacteristic Context triple: [BWh, hasCloudCoverCharacteristic, low annual cloudiness]
-
A.
summitOftenCloudCovered
Indicates that the summit of something is frequently or typically covered by clouds.
-
B.
hasCloudComposition
Indicates that an atmospheric body or region possesses a specific composition or makeup of clouds.
-
C.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
D.
hasAtmosphericFeature
chosen
Indicates that one entity possesses or exhibits a particular feature or characteristic of its atmosphere.
-
E.
hasNebulosity
Indicates that one entity possesses or exhibits nebulous, cloud-like, or diffuse characteristics associated with nebulosity.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea8779c081908171c58d345d54ae |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.