Triple
T11524016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyakojima |
E273240
|
entity |
| Predicate | hasPrefecturalCode |
P99937
|
FINISHED |
| Object | Okinawa Prefecture code 47 |
—
|
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: Okinawa Prefecture code 47 | Statement: [Miyakojima, hasPrefecturalCode, Okinawa Prefecture code 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrefecturalCode Context triple: [Miyakojima, hasPrefecturalCode, Okinawa Prefecture code 47]
-
A.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
B.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
C.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
D.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
-
E.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
- F. None of above. chosen
Provenance (4 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd26648819083de19bcddf8ad69 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.