Triple
T18686059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikephoros III Botaneiates |
E456865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine military commander |
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 military commander Context triple: [Nikephoros III Botaneiates, instanceOf, Byzantine military commander]
-
A.
Persian military commander
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
-
B.
Roman military commander
A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
-
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.
Athenian general
An Athenian general is a high-ranking military and political leader of ancient Athens responsible for commanding armies, planning campaigns, and often influencing civic decision-making.
-
E.
Georgian military commander
A Georgian military commander is a high-ranking officer from Georgia responsible for planning, directing, and overseeing military operations and strategy within the Georgian armed forces.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.