Triple
T17583465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badain Jaran Desert |
E428259
|
entity |
| Predicate | hasDuneHeight |
P18516
|
FINISHED |
| Object | over 500 meters |
—
|
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: over 500 meters | Statement: [Badain Jaran Desert, hasDuneHeight, over 500 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDuneHeight Context triple: [Badain Jaran Desert, hasDuneHeight, over 500 meters]
-
A.
duneHeightNearby
Indicates that the height of a sand dune in the vicinity of a given location or object is being specified or constrained.
-
B.
hasDuneType
Indicates that one entity is characterized by or associated with a specific type or classification of dune.
-
C.
highestDunesReach
chosen
Indicates that the maximum height or extent of sand dunes reaches or attains a specified level, point, or location.
-
D.
hasDunes
Indicates that one entity (typically a geographic area or surface) possesses or is characterized by sand dunes.
-
E.
notableDune
Indicates that something is a particularly significant or well-known sand dune, distinguished from ordinary dunes by its prominence, uniqueness, or recognition.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d015fc8190b2dd897026d6fcb5 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.