Triple
T2613778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamato polity |
E58837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Japanese political entity |
C4291
|
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: ancient Japanese political entity Context triple: [Yamato polity, instanceOf, ancient Japanese political entity]
-
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.
ancient kingdom
chosen
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
C.
metropolis of Japan
A metropolis of Japan is a highly urbanized, densely populated city designated as a major political, economic, and cultural center within the country.
-
D.
designated city of Japan
A designated city of Japan is a large municipality with a population over 500,000 that has been granted special administrative status by the national government, allowing it to perform many functions normally handled by prefectural governments.
-
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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:50 p.m.