Triple
T8551012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hegra |
E202443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nabataean settlement |
C24619
|
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: Nabataean settlement Context triple: [Hegra, instanceOf, Nabataean settlement]
-
A.
Nubian settlement
A Nubian settlement is a community or village inhabited by Nubian people, characterized by distinctive architectural styles, social organization, and cultural practices shaped by the Nile Valley environment and long-standing regional traditions.
-
B.
Numidian settlement
A Numidian settlement is a community or town established by the ancient Numidian people of North Africa, typically characterized by fortified hilltop locations, mixed pastoral-agricultural economies, and cultural influences from both indigenous Berber traditions and Mediterranean civilizations.
-
C.
ancient Nubian site
An ancient Nubian site is an archaeological location in the Nile Valley region of Nubia that preserves the material remains, architecture, and cultural landscapes of the historic Nubian civilizations.
-
D.
ancient rock-hewn cave city
An ancient rock-hewn cave city is a sprawling settlement carved directly into cliffs or mountainsides, featuring interconnected dwellings, temples, and passageways sculpted from living stone.
-
E.
Urartian archaeological site
An Urartian archaeological site is a location containing the material remains—such as fortresses, temples, settlements, and artifacts—of the Iron Age kingdom of Urartu, offering evidence of its political, economic, and religious life.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:19 p.m.