Triple
T17821692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 千歳市 |
E444999
|
entity |
| Predicate | 管轄法務局支局 |
P111469
|
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.
governedBranch
Indicates that one entity exercises governing authority or control over a particular branch or subdivision of an organization, institution, or system.
-
B.
managementJurisdiction
Indicates that one entity has formal authority or responsibility to manage, oversee, or administer another entity or domain within a defined scope or area.
-
C.
clericalBranchOf
Indicates that one entity functions as an administrative or clerical subdivision or office that is part of another, larger organizational entity.
-
D.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
E.
mayHaveJurisdictionOver
chosen
Indicates that one authority, entity, or body is potentially empowered to exercise legal or official control over another entity, case, or matter.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48911b660819097fc7ea94665a02a |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:15 a.m.