Triple
T35293911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carroccio |
E1019304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Italian military equipment |
C40700
|
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 Italian military equipment Context triple: [Carroccio, instanceOf, medieval Italian military equipment]
-
A.
Renaissance armour
Renaissance armour is a highly crafted, often ornate protective metal covering worn by European soldiers and nobles between the 14th and 17th centuries, reflecting both advances in metallurgy and the era’s artistic aesthetics.
-
B.
medieval military force
chosen
A medieval military force is an organized body of armed personnel, including knights, infantry, archers, and support units, raised and commanded by a lord, king, or other authority to wage war, defend territory, and enforce political power during the Middle Ages.
-
C.
Italian weapon
An Italian weapon is any tool or instrument of combat, offense, or defense that originates from or is primarily associated with Italian design, manufacture, or historical use.
-
D.
medieval artillery piece
A medieval artillery piece is a large, often wheeled weapon such as a catapult, trebuchet, or bombard designed to hurl heavy projectiles over distance to breach fortifications or attack enemy forces.
-
E.
medieval European sword
A medieval European sword is a double-edged, bladed weapon with a hilt and crossguard, designed primarily for cutting and thrusting in close combat and used by knights and soldiers throughout the Middle Ages.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.