Triple
T15906753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Place of Sacrifice |
E385738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nabataean altar complex |
C2557
|
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 altar complex Context triple: [High Place of Sacrifice, instanceOf, Nabataean altar complex]
-
A.
Nabataean settlement
A Nabataean settlement is an ancient community site established by the Nabataean civilization, typically characterized by rock-cut architecture, sophisticated water management systems, and strategic placement along trade routes in the Near East.
-
B.
Phoenician necropolis
A Phoenician necropolis is a burial complex or cemetery used by the ancient Phoenician civilization, typically featuring rock-cut tombs, sarcophagi, and grave goods that reflect their funerary practices and beliefs about the afterlife.
-
C.
Umayyad desert palace
An Umayyad desert palace is an early Islamic rural complex, often located in arid or steppe regions, combining residential, administrative, agricultural, and sometimes defensive and bathhouse functions for Umayyad elites.
-
D.
Punic sanctuary
A Punic sanctuary is a religious complex used by the ancient Carthaginians and related Phoenician communities for the worship of their deities, often featuring open-air altars, temples, votive offerings, and ritual installations.
-
E.
ancient sanctuary
chosen
An ancient sanctuary is a sacred, often secluded place dedicated to worship, ritual, or protection, typically imbued with religious or spiritual significance by past civilizations.
- F. None of above.
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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.