Triple
T12157133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simpson Desert |
E289601
|
entity |
| Predicate | hasDuneOrientation |
P69410
|
FINISHED |
| Object | north-south |
—
|
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: north-south | Statement: [Simpson Desert, hasDuneOrientation, north-south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDuneOrientation Context triple: [Simpson Desert, hasDuneOrientation, north-south]
-
A.
hasDuneType
Indicates that one entity is characterized by or associated with a specific type or classification of dune.
-
B.
hasDunes
Indicates that one entity (typically a geographic area or surface) possesses or is characterized by sand dunes.
-
C.
orientationOfMainDunes
chosen
Indicates the directional alignment or bearing of the primary dune formations relative to a reference frame.
-
D.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
E.
hasFieldOrientation
Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.