Triple
T27800753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mito Domain |
E702234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese historical domain |
C53361
|
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: Japanese historical domain Context triple: [Mito Domain, instanceOf, Japanese historical domain]
-
A.
historical province of Japan
A historical province of Japan is a former administrative and geographic division that existed before the modern prefecture system, often retaining cultural and historical significance in regional identity.
-
B.
Japanese historical event
A Japanese historical event is a significant occurrence in Japan’s past—such as a political shift, conflict, cultural transformation, or natural disaster—that notably influenced the nation’s society, governance, or cultural development.
-
C.
former district of Japan
A former district of Japan is an administrative subdivision that once existed within a prefecture but has since been dissolved or merged due to municipal reorganization.
-
D.
Japanese state
The Japanese state is the centralized political and legal authority governing Japan, encompassing its institutions, laws, territory, and international sovereignty.
-
E.
Japanese historical tale
A Japanese historical tale is a narrative work that recounts and embellishes real past events, figures, and battles in Japan’s history, blending factual record with literary storytelling.
- F. None of above. chosen
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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:34 p.m.