Triple
T18600211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大分県 |
E454597
|
entity |
| Predicate | 県庁所在地の行政区分 |
P100332
|
FINISHED |
| Object | 中核市・大分市 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 中核市・大分市 | Statement: [大分県, 県庁所在地の行政区分, 中核市・大分市]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 県庁所在地の行政区分 Context triple: [大分県, 県庁所在地の行政区分, 中核市・大分市]
-
A.
hasCountyAdministration
Indicates that an entity is governed, managed, or served by a specific county-level administrative authority.
-
B.
headquartersAdministrativeTerritory
chosen
Indicates that an entity serves as the administrative headquarters or seat of government for a specified territory or jurisdiction.
-
C.
inCountySeatRegionOf
Indicates that a county seat is located within and serves as the administrative center for a specified region.
-
D.
seatOfCountyAdministrativeBoard
Indicates that a location serves as the official seat or headquarters of a county-level administrative board.
-
E.
roleInAdministrativeDivision
Indicates that an entity holds or fulfills a specific role, function, or position within a particular administrative division or jurisdiction.
- F. None of above.
Provenance (3 batches)
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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5475018548190a2f497081af7ce55 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.