Triple
T18890308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | socii of Rome |
E462068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman allies |
C27053
|
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: Roman allies Context triple: [socii of Rome, instanceOf, Roman allies]
-
A.
ancient Roman ally
chosen
An ancient Roman ally is a foreign individual, city, or state that entered into a formal relationship with Rome—often through treaties or agreements—providing military or political support in exchange for protection, privileges, or limited autonomy.
-
B.
Roman political alliance
A Roman political alliance is a formal or informal partnership between individuals, factions, or states in ancient Rome formed to consolidate power, advance mutual political interests, and influence governance and decision-making.
-
C.
Roman legion
A Roman legion is a large, highly organized military unit of the ancient Roman army, typically composed of several thousand heavily armed infantry supported by cavalry and specialized troops.
-
D.
Roman auxiliary units
Roman auxiliary units were non-citizen military formations that supported the legions by providing specialized troops—such as infantry, cavalry, and archers—from diverse provincial populations across the empire.
-
E.
Sarmatian people
The Sarmatian people were an ancient Iranian-speaking nomadic group who inhabited the Eurasian steppe north of the Black Sea from around the 5th century BCE to the 4th century CE, known for their skilled cavalry and influence on neighboring cultures, including the Romans.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:58 a.m.