Triple
T33026174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crossing of the Rub' al Khali |
E845048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical expedition |
C61641
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical expedition Context triple: [crossing of the Rub' al Khali, instanceOf, historical expedition]
-
A.
historical expedition party
A historical expedition party is a group of individuals organized in the past to undertake a significant journey or exploration, often for purposes of discovery, trade, conquest, or scientific investigation.
-
B.
archaeological expedition
An archaeological expedition is a planned scientific journey undertaken by researchers to locate, excavate, and analyze material remains of past human cultures at specific sites.
-
C.
multinational expedition
A multinational expedition is a coordinated journey or mission involving participants, resources, and leadership from multiple countries working together toward shared exploratory, scientific, or strategic objectives.
-
D.
19th-century scientific expedition
A 19th-century scientific expedition is a long-distance, often state- or institution-sponsored journey undertaken by researchers and explorers to collect data, specimens, and observations about unfamiliar regions, peoples, and natural phenomena using the scientific methods and technologies of the time.
-
E.
imperial journeys
Imperial journeys are state-sponsored expeditions or travels undertaken by or on behalf of an empire to assert power, expand influence, administer territories, or display prestige across its domains.
- F. None of above. chosen
Provenance (1 batch)
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.