Triple
T16973381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Argentarius |
E411744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine financier |
C19516
|
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: Byzantine financier Context triple: [Julius Argentarius, instanceOf, Byzantine financier]
-
A.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
-
B.
Jewish financier
A Jewish financier is a financial professional of Jewish heritage who engages in activities such as investment, banking, or capital management, shaped by but not reducible to their cultural and religious background.
-
C.
Italian banker
An Italian banker is a financial professional from Italy who manages banking operations such as lending, investments, and client accounts within the Italian and international financial systems.
-
D.
Byzantine person
chosen
A Byzantine person is an individual who lived in or was culturally associated with the Byzantine Empire, characterized by its Eastern Roman heritage, Orthodox Christian faith, and rich traditions in art, law, and administration.
-
E.
Byzantine jurist
A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.