Triple
T13962307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sealand |
E335826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Mesopotamian region |
C25297
|
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: ancient Mesopotamian region Context triple: [Sealand, instanceOf, ancient Mesopotamian region]
-
A.
region of ancient Mesopotamia
chosen
A region of ancient Mesopotamia is a geographically defined area within the broader Mesopotamian landscape, characterized by shared political, cultural, and economic features during a specific historical period.
-
B.
Mesopotamian city
A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
-
C.
Mesopotamian mythological place
A Mesopotamian mythological place is a legendary or sacred location from ancient Mesopotamian belief systems, such as heavens, underworlds, or divine cities, that features in myths, religious texts, and ritual narratives.
-
D.
Mesopotamian period
The Mesopotamian period refers to the ancient era in the region between the Tigris and Euphrates rivers, marked by the rise of early urban civilizations, writing systems, and complex social, political, and religious structures.
-
E.
historical region mentioned in Egyptian texts
A historical region mentioned in Egyptian texts is a geographically or culturally distinct area referenced in ancient Egyptian writings, inscriptions, or records, recognized for its role in Egypt’s political, economic, or religious interactions.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.