Triple
T16534971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amakusa Islands |
E401667
|
entity |
| Predicate | majorTown |
P316
|
FINISHED |
| Object | Reihoku |
—
|
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: Reihoku | Statement: [Amakusa Islands, majorTown, Reihoku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reihoku Context triple: [Amakusa Islands, majorTown, Reihoku]
-
A.
Reihoku
chosen
Reihoku is a coastal town located on the Amakusa Islands in Kumamoto Prefecture, Japan, known for its fishing industry and scenic seaside landscapes.
-
B.
Taihoku
Taihoku was the Japanese colonial-era name for Taipei, which served as the administrative and political center of Taiwan under Japanese rule.
-
C.
Uraku
Uraku is a Japanese surname associated with individuals such as Akinobu Uraku.
-
D.
Izunokuni
Izunokuni is a city in Shizuoka Prefecture, Japan, known for its hot springs, historical sites, and scenic views on the Izu Peninsula.
-
E.
Ryōtsu
Ryōtsu was a former city on Sado Island in Niigata Prefecture, Japan, known for its coastal setting and later incorporation into the city of Sado.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e345574d88819094548367bf983078 |
completed | April 18, 2026, 8:48 a.m. |
Created at: April 10, 2026, 5:15 a.m.