Triple
T17331150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kagoshima Bay |
E420817
|
entity |
| Predicate | isInPrefecturalCapitalRegion |
P33552
|
FINISHED |
| Object | Kagoshima City |
—
|
NE NERFINISHED |
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: Kagoshima City | Statement: [Kagoshima Bay, isInPrefecturalCapitalRegion, Kagoshima City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPrefecturalCapitalRegion Context triple: [Kagoshima Bay, isInPrefecturalCapitalRegion, Kagoshima City]
-
A.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
B.
locatedInPrefectureCapitalRegion
chosen
Indicates that the subject is geographically situated within the capital region of a given prefecture.
-
C.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
-
D.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
E.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d6870c8190989897aa6beba8ff |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.