Triple
T24365418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōkimi |
E614180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Japanese office |
C2921
|
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 office Context triple: [Ōkimi, instanceOf, ancient Japanese office]
-
A.
Japanese imperial office
chosen
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.
-
B.
traditional Japanese residence
A traditional Japanese residence is a wooden, often single-story home characterized by tatami-mat rooms, sliding shoji doors, engawa verandas, and a close integration with nature and seasonal changes.
-
C.
Edo-period architecture
Edo-period architecture refers to the Japanese building styles from the early 17th to mid-19th centuries characterized by wooden construction, modular interiors, sliding doors, tatami flooring, and a balance of simplicity, functionality, and refined ornamentation seen in castles, temples, townhouses, and teahouses.
-
D.
Japanese gate
A Japanese gate is a traditional architectural structure, often called a torii or mon, that marks the entrance to a sacred or significant space and symbolically separates the mundane world from the spiritual or special area beyond.
-
E.
Daibutsu
Daibutsu is a monumental statue of the Buddha, typically cast in bronze or carved in stone, that serves as a grand focal point of worship and cultural heritage in Japanese Buddhist temples.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:01 a.m.