Triple
T35032229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | megas doux |
E1010811
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine naval office |
C6535
|
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 naval office Context triple: [megas doux, instanceOf, Byzantine naval office]
-
A.
Byzantine warship
A Byzantine warship is a fast, oared and sailed naval vessel of the Eastern Roman (Byzantine) Empire, typically equipped with a ram and siphons for projecting Greek fire, designed for coastal defense, convoy escort, and Mediterranean sea control.
-
B.
naval office
A naval office is an administrative entity within a navy responsible for managing operations, logistics, personnel, and documentation related to maritime military activities.
-
C.
Byzantine official
chosen
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.
-
D.
Byzantine institution
A Byzantine institution is a formal organization or structure within the Byzantine Empire—such as its imperial bureaucracy, church hierarchy, legal system, or military administration—defined by complex procedures, centralized authority, and a fusion of Roman, Christian, and local traditions.
-
E.
Venetian admiral
A Venetian admiral is a high-ranking naval commander of the Republic of Venice responsible for leading its fleets, safeguarding maritime trade routes, and directing naval warfare in the Mediterranean and beyond.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.