Triple
T33329854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秋田県立湯沢高等学校 |
E853371
|
entity |
| Predicate | 所在自治体の行政区分 |
P35772
|
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.
通過自治体
Indicates that something is processed, managed, or carried out through a local government or municipal authority.
-
B.
isAdministrativeDivision
Indicates that one entity functions as an official administrative subdivision or jurisdiction within the governance structure of another entity.
-
C.
usesAdministrativeDivisionType
chosen
Indicates that one entity employs or applies a particular type of administrative division as part of its territorial or organizational structure.
-
D.
containsAdministrativeTerritory
Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
-
E.
roleInAdministrativeDivision
Indicates that an entity holds or fulfills a specific role, function, or position within a particular administrative division or jurisdiction.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.