Triple
T16564002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokkō Airando |
E402409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Kobe |
C37633
|
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: district of Kobe Context triple: [Rokkō Airando, instanceOf, district of Kobe]
-
A.
district of Osaka
A district of Osaka is an administrative subdivision within the city or prefecture of Osaka, characterized by its own local governance, neighborhoods, and community services.
-
B.
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.
-
C.
district of Japan
A district of Japan is an administrative unit within a prefecture that groups together multiple towns and villages, serving primarily as a geographic and statistical subdivision rather than a governing body.
-
D.
special ward of Osaka City
A special ward of Osaka City is a proposed administrative subdivision that would function with a high degree of local autonomy under Osaka’s metropolitan-style governance, similar to Tokyo’s special wards.
-
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. 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.