Triple
T30620302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubbah |
E779426
|
entity |
| Predicate | hasNearbyDuneField |
P37774
|
FINISHED |
| Object | Great Nefud Desert |
—
|
NE NERFINISHED |
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: Great Nefud Desert | Statement: [Jubbah, hasNearbyDuneField, Great Nefud Desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyDuneField Context triple: [Jubbah, hasNearbyDuneField, Great Nefud Desert]
-
A.
hasNearbyDesert
chosen
Indicates that one entity is located close to or in the vicinity of a desert region associated with another entity.
-
B.
duneHeightNearby
Indicates that the height of a sand dune in the vicinity of a given location or object is being specified or constrained.
-
C.
hasNearbyOilField
Indicates that an entity is located close to or in the vicinity of an oil field.
-
D.
isMajorDuneFieldOf
Indicates that one entity is the primary or dominant dune field associated with, or located within, another entity (such as a region or planetary body).
-
E.
isLocatedInDesert
Indicates that something exists or is situated within a desert region or environment.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: April 29, 2026, 8:27 p.m.