Triple
T25096328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kita Ward, Kumamoto |
E628598
|
entity |
| Predicate | locatedInPrefectureCapital |
P103943
|
FINISHED |
| Object | Kumamoto 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: Kumamoto City | Statement: [Kita Ward, Kumamoto, locatedInPrefectureCapital, Kumamoto City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPrefectureCapital Context triple: [Kita Ward, Kumamoto, locatedInPrefectureCapital, Kumamoto City]
-
A.
locatedInPrefectureCapitalRegion
Indicates that the subject is geographically situated within the capital region of a given prefecture.
-
B.
isInPrefecturalCapital
chosen
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
C.
locatedInPrefectureLevelCity
Indicates that one entity is geographically situated within the jurisdiction or boundaries of a prefecture-level city.
-
D.
prefectureCapital
Indicates that a city serves as the administrative capital of a given prefecture.
-
E.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 18, 2026, 6:25 a.m.