Triple
T30195420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Sands gypsum dunes |
E767612
|
entity |
| Predicate | reasonForCoolSand |
P186464
|
FINISHED |
| Object | high reflectivity of gypsum |
—
|
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: high reflectivity of gypsum | Statement: [White Sands gypsum dunes, reasonForCoolSand, high reflectivity of gypsum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCoolSand Context triple: [White Sands gypsum dunes, reasonForCoolSand, high reflectivity of gypsum]
-
A.
hasSand
Indicates that something contains, is covered with, or is characterized by the presence of sand.
-
B.
hasSandColor
Indicates that one entity possesses or exhibits the sand-like color of another entity or color value.
-
C.
reasonForDesiccation
Indicates the cause or factor responsible for something becoming dried out or losing its moisture.
-
D.
reasonForOutdoorSetting
Indicates the explanation or cause for why an event or situation is taking place in an outdoor setting.
-
E.
reasonForNeutralSite
Indicates that there is an identified justification or cause for choosing a neutral location for an event or interaction between parties.
- F. None of above. chosen
Provenance (4 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 29, 2026, 7:29 p.m.