Triple
T21519969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 都筑郡 |
E530945
|
entity |
| Predicate | 関連行政区画の変遷 |
P124980
|
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.
partOfAdministrativeDivisionReform
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
B.
hasTerritoryReorganizedInto
chosen
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
-
C.
territorialChange
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
-
D.
regionTransformed
Indicates that one region has been changed or converted into another region through some transformation process.
-
E.
urbanDivisionRelation
Indicates a relationship where one urban area, zone, or administrative unit is divided into, or associated with, specific sub-areas or subdivisions within a city or metropolitan region.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884af0f08190bc1f3d70e57a325d |
completed | April 26, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.