Triple
T28813330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北岳 |
E727573
|
entity |
| Predicate | 所属自治体 |
P158179
|
FINISHED |
| Object | 山梨県南アルプス市周辺の山域 |
—
|
NE NERFINISHED |
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 something is processed, managed, or carried out through a local government or municipal authority.
-
B.
行政区
chosen
Indicates a relationship where one entity is an administrative division or jurisdictional area associated with, governed by, or belonging to another entity.
-
C.
isPartOfMunicipalityType
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
D.
servesAsMunicipalAuthorityFor
Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
-
E.
locatedInMunicipalAssociation
Indicates that an entity (typically a municipality or locality) is situated within and belongs administratively to a specific municipal association.
- 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_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.