Triple
T11192655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Sandy Desert |
E264838
|
entity |
| Predicate | hasSandDuneOrientation |
P69410
|
FINISHED |
| Object | generally east–west |
—
|
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: generally east–west | Statement: [Great Sandy Desert, hasSandDuneOrientation, generally east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSandDuneOrientation Context triple: [Great Sandy Desert, hasSandDuneOrientation, generally east–west]
-
A.
orientationOfMainDunes
chosen
Indicates the directional alignment or bearing of the primary dune formations relative to a reference frame.
-
B.
cliffOrientation
Indicates the directional facing or alignment of a cliff relative to a reference frame (e.g., compass direction or slope aspect).
-
C.
hasCoastalDuneSystem
Indicates that an area or region possesses a natural coastal dune system along its shoreline.
-
D.
coastOrientation
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
E.
valleyOrientation
Indicates the directional alignment or bearing along which a valley extends across the landscape.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8be025481909d311b587418dfb2 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.