Triple
T19949357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arikamedu |
E479514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-Roman trading center |
C7015
|
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: Indo-Roman trading center Context triple: [Arikamedu, instanceOf, Indo-Roman trading center]
-
A.
ancient urban center
An ancient urban center is a densely populated, historically significant settlement that served as a focal point for political, economic, religious, and cultural activities in early civilizations.
-
B.
ancient port city
chosen
An ancient port city is a historical urban center located on a coast or navigable waterway that served as a hub for maritime trade, cultural exchange, and strategic defense.
-
C.
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.
-
D.
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.
-
E.
Indus Valley Civilization site
An Indus Valley Civilization site is an archaeological location associated with the Bronze Age urban culture of the northwestern Indian subcontinent, characterized by planned cities, advanced drainage systems, and material remains reflecting complex social, economic, and religious life.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.