Triple
T12740348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opera Nazionale Combattenti |
E304471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian state organization |
C18094
|
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: Italian state organization Context triple: [Opera Nazionale Combattenti, instanceOf, Italian state organization]
-
A.
Italian state
An Italian state is a historically or politically defined territorial entity on the Italian peninsula, governed by its own institutions and authorities within a specific period or constitutional framework.
-
B.
Italian administrative division
An Italian administrative division is a territorial unit within Italy’s governmental hierarchy, such as a region, province, or municipality, that serves as a level of local governance and public administration.
-
C.
Italian city-state
An Italian city-state is an independent, self-governing urban center and its surrounding territory on the Italian peninsula, typically flourishing in the medieval and Renaissance periods through commerce, politics, and culture.
-
D.
Italian military organization
An Italian military organization is a structured entity within Italy’s armed forces responsible for planning, coordinating, and executing defense, security, and operational activities according to national and international directives.
-
E.
Italian institution
chosen
An Italian institution is an organization or establishment, public or private, that operates within Italy’s legal, cultural, and social framework to provide governance, services, education, or cultural preservation.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.