Triple
T20225765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court Medical Service |
E495373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial court institution |
C6483
|
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 court institution Context triple: [Court Medical Service, instanceOf, imperial court institution]
-
A.
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.
-
B.
imperial institution
chosen
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
-
C.
royal court
A royal court is the formal assembly of a monarch’s household, advisors, officials, and attendants who support, counsel, and ceremonially represent the sovereign’s authority and governance.
-
D.
imperial estate
An imperial estate is a large, centrally administered landholding owned or controlled by an emperor or imperial authority, typically encompassing agricultural, residential, and administrative functions that support the imperial household and governance.
-
E.
Japanese imperial office
A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:39 p.m.