Triple
T24952034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北小島 |
E624365
|
entity |
| Predicate | 属する行政区画 |
P128478
|
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.
partOfPrefecture
Indicates that one entity is a subdivision or component that belongs administratively or geographically to a given prefecture.
-
B.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
C.
subprefectureOf
Indicates that one administrative subprefecture is a subordinate division within and officially belongs to a larger governing region or prefecture.
-
D.
governmentalDistrictOf
chosen
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
E.
containsAdministrativeTerritory
Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f424004d588190abe0115931aab67a |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:57 a.m.