Triple
T21719999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asuka-mura |
E536128
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Amakashi-no-oka |
—
|
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: Amakashi-no-oka | Statement: [Asuka-mura, contains, Amakashi-no-oka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amakashi-no-oka Context triple: [Asuka-mura, contains, Amakashi-no-oka]
-
A.
Amakashi-no-oka
chosen
Amakashi-no-oka is a historic hill in Japan’s Asuka region, known as an ancient political and cultural center associated with early Japanese state formation.
-
B.
Mihama
Mihama is a coastal town in Aichi Prefecture, Japan, known for its seaside scenery and role as part of the Chita Peninsula region.
-
C.
Omishima
Omishima is a scenic island in Japan’s Seto Inland Sea, known for its cycling route on the Shimanami Kaido, historic Oyamazumi Shrine, and coastal landscapes.
-
D.
Yumenoshima
Yumenoshima is a reclaimed island in Tokyo Bay known for its parks, sports and recreational facilities, and former landfill history.
-
E.
Omori-kaigan
Omori-kaigan is a coastal neighborhood in Ōta Ward, Tokyo, known for its residential character and proximity to Tokyo Bay.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96de818819084c268d4775a8e3a |
completed | April 27, 2026, 9:47 p.m. |
Created at: April 16, 2026, 6:47 p.m.