Triple
T14833125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unzen |
E348757
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Unzen City |
E348757
|
NE 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: Unzen City | Statement: [Unzen, nearCity, Unzen City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unzen City Context triple: [Unzen, nearCity, Unzen City]
-
A.
Unzen
chosen
Unzen is an active volcanic complex on Japan’s Kyushu Island known for its destructive eruptions and associated pyroclastic flows.
-
B.
Iizuka
Iizuka is a city in Fukuoka Prefecture, Japan, known historically for its coal mining industry and now as a regional commercial and residential center.
-
C.
Kusatsu
Kusatsu is a Japanese city in Shiga Prefecture known as a regional commercial hub and transportation crossroads near Lake Biwa.
-
D.
Izumisano
Izumisano is a coastal city in Osaka Prefecture, Japan, known as the mainland gateway to Kansai International Airport and a hub for regional commerce and travel.
-
E.
Kōka
Kōka is a city in Shiga Prefecture, Japan, historically famous as the home of the Kōga ninja tradition.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded075af0881908fb35a9e7ee46749 |
completed | April 14, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff133571008190b7e7867208095b90 |
completed | May 9, 2026, 10:57 a.m. |
Created at: April 10, 2026, 1:52 a.m.