Triple
T28813195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 甲信越地方 |
E727571
|
entity |
| Predicate | regionCodeUsage |
P156800
|
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: [甲信越地方, regionCodeUsage, 統計上の地域区分]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCodeUsage Context triple: [甲信越地方, regionCodeUsage, 統計上の地域区分]
-
A.
regionCodeUsedIn
chosen
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
B.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
C.
regionCodeMeaning
Indicates that a region code is associated with its corresponding descriptive meaning or label.
-
D.
regionCodeCountApprox
Indicates an approximate count of distinct region codes associated with the given context or dataset.
-
E.
regionCodePattern
Indicates the standardized format or pattern that valid region codes must follow.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 28, 2026, 6:31 a.m.