Triple
T13705400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamo River dining terraces |
E328626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kyoto cultural feature |
C34072
|
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: Kyoto cultural feature Context triple: [Kamo River dining terraces, instanceOf, Kyoto cultural feature]
-
A.
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.
-
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.
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.
-
D.
core city of Japan
A core city of Japan is a mid-sized municipality designated by the national government that has been delegated many administrative functions normally handled by prefectures, allowing it greater local autonomy and responsibility.
-
E.
Japanese cultural center
A Japanese cultural center is a community-focused institution that promotes understanding and appreciation of Japanese culture through language classes, arts and crafts workshops, cultural events, and educational programs.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.