Triple
T6070909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soprintendenza Speciale per i Beni Archeologici di Roma |
E135277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian public institution |
C14097
|
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 public institution Context triple: [Soprintendenza Speciale per i Beni Archeologici di Roma, instanceOf, Italian public institution]
-
A.
Italian institution
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.
-
B.
government agency of Italy
chosen
A government agency of Italy is a public organization established by the Italian state to perform specific administrative, regulatory, or service functions in support of national policies and public interests.
-
C.
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.
-
D.
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.
-
E.
Italian company
An Italian company is a business organization established under Italian law that operates for profit or specific purposes within Italy’s economic, legal, and cultural context.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:10 p.m.