Triple
T30515822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel Keppe |
E776562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian Christian town |
C56242
|
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: Assyrian Christian town Context triple: [Tel Keppe, instanceOf, Assyrian Christian town]
-
A.
Hebrew city
A Hebrew city is an urban settlement historically or presently inhabited by Hebrew-speaking or Jewish communities, characterized by its cultural, religious, and social institutions rooted in Hebrew and Jewish traditions.
-
B.
biblical city
A biblical city is an urban settlement referenced in the Bible, often serving as the setting for religious events, narratives, and teachings within the biblical tradition.
-
C.
Phrygian city
A Phrygian city is an ancient urban settlement located in the historical region of Phrygia in central Anatolia, characterized by its distinctive rock-cut architecture, religious monuments, and role in the Phrygian kingdom’s political and cultural life.
-
D.
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.
-
E.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:16 p.m.