Triple
T28119261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epaphroditus |
E710730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial secretary |
C49436
|
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: imperial secretary Context triple: [Epaphroditus, instanceOf, imperial secretary]
-
A.
imperial official
chosen
An imperial official is a government functionary appointed by a sovereign empire to administer its laws, collect revenues, and enforce imperial authority within a designated jurisdiction.
-
B.
cabinet secretary
A cabinet secretary is a senior government official who heads an executive department and advises the head of state or government on policy and administration within their area of responsibility.
-
C.
clerk of the Privy Seal
A clerk of the Privy Seal was an official responsible for preparing, drafting, and processing documents that required authentication by the monarch’s privy seal, often serving as an intermediary between petitioners and higher offices of royal administration.
-
D.
imperial governor
An imperial governor is a high-ranking official appointed by a central empire to administer, oversee, and enforce its authority, laws, and policies within a specific province or territory.
-
E.
imperial court office
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 9:16 p.m.