Triple
T16999661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tana |
E412408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval trading colony |
C37673
|
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: medieval trading colony Context triple: [Tana, instanceOf, medieval trading colony]
-
A.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
B.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
C.
medieval capital
A medieval capital is the carved topmost element of a column or pillar in Middle Ages architecture, often richly decorated with foliage, figures, or symbolic motifs to transition between the shaft and the structure it supports.
-
D.
historic confederation of towns
A historic confederation of towns is a formal alliance of multiple municipalities that cooperatively coordinate defense, trade, governance, or mutual support while retaining their individual local autonomy.
-
E.
Renaissance town
A Renaissance town is an urban settlement characterized by humanist-inspired planning, harmonious proportions, and architecture that blends classical forms with emerging civic, commercial, and cultural functions of the 14th–17th centuries.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.