Triple
T30441840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊丹市立図書館 |
E774465
|
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.
isAdministrativeDivision
Indicates that one entity functions as an official administrative subdivision or jurisdiction within the governance structure of another entity.
-
B.
administrativeTerritoryType
Indicates the classification of an administrative area according to its level or type of territorial governance (e.g., city, county, province).
-
C.
isCentralAdministrativeDivisionFor
Indicates that one administrative unit serves as the primary governing or managing division for another entity or territory.
-
D.
usesAdministrativeDivisionType
Indicates that one entity employs or applies a particular type of administrative division as part of its territorial or organizational structure.
-
E.
administrativeTerritorialEntityOf
chosen
Indicates that one entity serves as the administrative territorial unit or jurisdiction to which another entity belongs or is governed by.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6869948e481908901dbda23952cc0 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:08 p.m.