Triple
T5412991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florentine guilds |
E121055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval guild system |
C6688
|
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 guild system Context triple: [Florentine guilds, instanceOf, medieval guild system]
-
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.
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.
-
D.
medieval institution
chosen
A medieval institution is an organized social, political, religious, or economic structure—such as the Church, feudal lordship, or guilds—that governed relationships, authority, and daily life in medieval society.
-
E.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:05 p.m.