Triple
T23372025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 松輪島 |
E593499
|
entity |
| Predicate | 所属行政区画 |
P35059
|
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.
rankInChineseAdministrativeHierarchy
Indicates the relative level or position an administrative unit holds within the formal hierarchy of Chinese government administration.
-
B.
administrativeTerritoryType
Indicates the classification of an administrative area according to its level or type of territorial governance (e.g., city, county, province).
-
C.
administrativeTerritorialEntityOf
chosen
Indicates that one entity serves as the administrative territorial unit or jurisdiction to which another entity belongs or is governed by.
-
D.
containsAdministrativeTerritory
Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
-
E.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.