Triple
T6140501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Sand Sea |
E136947
|
entity |
| Predicate | duneHeight |
P18516
|
FINISHED |
| Object | dunes up to several tens of meters high |
—
|
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: dunes up to several tens of meters high | Statement: [Great Sand Sea, duneHeight, dunes up to several tens of meters high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duneHeight Context triple: [Great Sand Sea, duneHeight, dunes up to several tens of meters high]
-
A.
damHeight
Indicates the vertical height of a dam structure, typically measured from its base or foundation to its crest.
-
B.
highestDunesReach
chosen
Indicates that the maximum height or extent of sand dunes reaches or attains a specified level, point, or location.
-
C.
notableDune
Indicates that something is a particularly significant or well-known sand dune, distinguished from ordinary dunes by its prominence, uniqueness, or recognition.
-
D.
highestPyramidHeight
Indicates the maximum vertical height reached by any pyramid in a given context or set.
-
E.
deckHeightAboveValley
Indicates that the height of a deck is measured relative to, and positioned above, the elevation of a valley.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb030fc8190b78e4967eea65611 |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.