Triple
T31064567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | imperial fiscus |
E791631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman financial institution |
C60060
|
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 financial institution Context triple: [imperial fiscus, instanceOf, Roman financial institution]
-
A.
Roman financial institution
chosen
A Roman financial institution is an organized entity in ancient Rome that managed monetary transactions such as lending, deposits, currency exchange, and public or private financing within the Roman economic and legal framework.
-
B.
Vatican bank
The Vatican bank is the financial institution of the Holy See that manages assets and provides banking services primarily for the Catholic Church, religious orders, and Vatican employees.
-
C.
Roman cultural institution
A Roman cultural institution is an organized social, religious, political, or recreational structure—such as temples, forums, baths, theaters, or legal bodies—that shaped and reflected the values, practices, and public life of ancient Roman society.
-
D.
Samnite institution
A Samnite institution is a formalized social, political, or religious structure within ancient Samnite society that organized communal life, governance, and cultural practices.
-
E.
organ of Banca d’Italia
An organ of Banca d’Italia is an institutional body or governing component within the central bank that is formally entrusted with specific decision-making, supervisory, or administrative functions in pursuit of its statutory objectives.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:01 p.m.