Triple
T25096101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 熊本市 |
E628592
|
entity |
| Predicate | 行政区 |
P44156
|
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.
郡
Indicates that the subject municipality is administratively located within the specified district.
-
B.
cityAdministrativeRegion
Indicates that a city is located within or governed by a specific administrative region (such as a state, province, or similar jurisdiction).
-
C.
administrativeDistricts
chosen
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
D.
administrativeOkrug
Indicates that one entity functions as an administrative district or okrug governing or encompassing another entity within an administrative hierarchy.
-
E.
administrativeCouncilArea
Indicates that one entity is an administrative council area within which the other entity is located or governed.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:25 a.m.