Triple
T38292862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safavid garrison of Isfahan |
E1022407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Safavid military unit |
C63905
|
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: Safavid military unit Context triple: [Safavid garrison of Isfahan, instanceOf, Safavid military unit]
-
A.
component of Ottoman army
A component of the Ottoman army is a distinct organizational, functional, or tactical unit—such as infantry, cavalry, artillery, or auxiliary corps—that collectively contributed to the empire’s military structure and operations.
-
B.
Papal military unit
A Papal military unit is an organized armed force historically raised, controlled, or sanctioned by the Pope or the Papal States to defend papal authority, territories, and interests.
-
C.
Venetian military unit
A Venetian military unit is an organized group of soldiers, sailors, or specialized forces raised, equipped, and commanded by the Republic of Venice to defend its territories, protect its maritime trade routes, and conduct land and naval warfare.
-
D.
ancient cavalry unit
An ancient cavalry unit is a military formation composed of mounted soldiers trained to fight from horseback, used for rapid movement, shock attacks, reconnaissance, and flanking maneuvers on the battlefield.
-
E.
Jewish military unit
A Jewish military unit is an organized armed force composed primarily of Jewish personnel, formed to conduct defense, combat, or security operations under a specific command structure.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.