Triple
T31200299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samnite League |
E795452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Samnite political organization |
C57262
|
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: Samnite political organization Context triple: [Samnite League, instanceOf, Samnite political organization]
-
A.
Samnite institution
chosen
A Samnite institution is a formalized social, political, or religious structure within ancient Samnite society that organized communal life, governance, and cultural practices.
-
B.
Etruscan political organization
Etruscan political organization consisted of independent city-states governed by powerful aristocratic elites and priest-kings, loosely united in a religious and political league that coordinated common interests without forming a centralized state.
-
C.
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.
-
D.
Samnite commander
A Samnite commander is a high-ranking military leader from the ancient Samnite tribes of central and southern Italy, responsible for organizing warriors, planning tactics, and leading them in battle against rival states such as Rome.
-
E.
Ligurian settlement
A Ligurian settlement is a historically or archaeologically identified inhabited place established or predominantly occupied by the ancient Ligurian people, characterized by their distinct cultural, social, and territorial attributes.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:09 p.m.