Triple
T31427428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokashiki |
E801701
|
entity |
| Predicate | hasPrefectureCode |
P99937
|
FINISHED |
| Object | 47 (Okinawa) |
—
|
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: 47 (Okinawa) | Statement: [Tokashiki, hasPrefectureCode, 47 (Okinawa)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrefectureCode Context triple: [Tokashiki, hasPrefectureCode, 47 (Okinawa)]
-
A.
hasPrefecturalCode
chosen
Indicates that an entity is associated with a specific prefectural identification code assigned by an administrative system.
-
B.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
C.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
-
D.
isAssociatedWithPrefecture
Indicates that an entity has a connection or affiliation with a specific prefecture, such as administrative, geographic, or organizational association.
-
E.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: April 30, 2026, 8:54 p.m.