Triple
T12716772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nefud Desert |
E303862
|
entity |
| Predicate | hasVisibilityCharacteristic |
P106322
|
FINISHED |
| Object | frequent sandstorms |
—
|
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: frequent sandstorms | Statement: [Nefud Desert, hasVisibilityCharacteristic, frequent sandstorms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisibilityCharacteristic Context triple: [Nefud Desert, hasVisibilityCharacteristic, frequent sandstorms]
-
A.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
-
B.
hasVisitorCharacteristic
Indicates that a visitor possesses or exhibits a particular characteristic, attribute, or quality.
-
C.
isVisibleAs
Indicates that one entity can be perceived or appears to observers under the form, name, or representation of another entity.
-
D.
hasVisualCharacter
Indicates that one entity possesses or exhibits a particular visual appearance, style, or graphical characteristic defined by another entity.
-
E.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620bd6148190a2f50067a4c18c14 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:23 p.m.