Triple
T36062666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heian-kyō (Kyoto, fictionalized) |
E1043129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictionalized version of Kyoto |
C7344
|
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: fictionalized version of Kyoto Context triple: [Heian-kyō (Kyoto, fictionalized), instanceOf, fictionalized version of Kyoto]
-
A.
Kyoto cultural feature
A Kyoto cultural feature is any distinctive tradition, practice, place, or artifact that embodies the historical, artistic, and spiritual heritage uniquely associated with the city of Kyoto.
-
B.
neighborhood of Kyoto
A neighborhood of Kyoto is a distinct local area within the city characterized by its blend of traditional machiya townhouses, temples or shrines, narrow streets, and community-focused shops and residences that reflect Kyoto’s historical and cultural identity.
-
C.
district of Kyoto
A district of Kyoto is an administrative or historically defined area within the city of Kyoto, characterized by its own local governance functions, cultural identity, and community infrastructure.
-
D.
fictional city
chosen
A fictional city is an imagined urban environment, complete with its own geography, culture, history, and social structures, created to serve as the setting for stories or speculative worlds.
-
E.
special ward of Kyoto City
A special ward of Kyoto City is a distinct administrative district within Kyoto that possesses a degree of local self-governance while remaining under the broader jurisdiction and services of the city government.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:08 p.m.