Triple
T22582656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka Prefectural Public Safety Commission |
E544605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government agency of Fukuoka Prefecture |
C17888
|
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: government agency of Fukuoka Prefecture Context triple: [Fukuoka Prefectural Public Safety Commission, instanceOf, government agency of Fukuoka Prefecture]
-
A.
special ward of Fukuoka City
A special ward of Fukuoka City is a designated administrative subdivision within Fukuoka that possesses a degree of local governmental authority and specialized services distinct from other municipal districts.
-
B.
government agency of Japan
A government agency of Japan is an official administrative body established by the Japanese government to implement laws, deliver public services, and manage specific policy areas at the national level.
-
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.
provincial government agency
chosen
A provincial government agency is a public-sector organization established by a provincial authority to implement policies, deliver services, and regulate activities within its jurisdiction.
-
E.
Japan Maritime Self-Defense Force district
A Japan Maritime Self-Defense Force district is a regional naval command area responsible for organizing, administering, and supporting JMSDF units and operations within its designated geographic zone.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:53 p.m.