Triple
T4300910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotorua |
E99832
|
entity |
| Predicate | hasSisterCity |
P919
|
FINISHED |
| Object | Beppu |
E87326
|
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: Beppu | Statement: [Rotorua, hasSisterCity, Beppu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beppu Context triple: [Rotorua, hasSisterCity, Beppu]
-
A.
Beppu
chosen
Beppu is a famous Japanese city on the island of Kyushu renowned for its numerous hot springs and geothermal attractions.
-
B.
Beppu Bay
Beppu Bay is a coastal bay in Ōita Prefecture on Japan’s Kyushu Island, known for its scenic shoreline and proximity to the hot spring resort city of Beppu.
-
C.
Sakurajima
Sakurajima is an active stratovolcano in Kagoshima Prefecture, Japan, known for its frequent eruptions and dramatic presence in Kagoshima Bay.
-
D.
Takachiho
Takachiho is a town in Miyazaki Prefecture, Japan, famed in mythology as a sacred site of the Japanese creation legends and early imperial origins.
-
E.
Shikotsu caldera
Shikotsu caldera is a large volcanic depression in Hokkaido, Japan, known for its scenic caldera lake and geothermal features.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509fb2b88190a13ab88a5b924052 |
completed | March 12, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5c74d59688190820cef42c4228a3a |
completed | March 14, 2026, 8:38 p.m. |
Created at: March 12, 2026, 11:08 p.m.