Triple

T4963932
Position Surface form Disambiguated ID Type / Status
Subject Higashiosaka E111473 entity
Predicate adjacentTo P224 FINISHED
Object Ikoma E176744 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: Ikoma | Statement: [Higashiosaka, adjacentTo, Ikoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ikoma
Context triple: [Higashiosaka, adjacentTo, Ikoma]
  • A. Ikoma chosen
    Ikoma is a city in Japan known for its scenic setting on the slopes of Mount Ikoma and its role as a residential and commuter hub near Osaka and Nara.
  • B. Shikaoi
    Shikaoi is a rural town in Hokkaido, Japan, known for its natural scenery, agriculture, and access to outdoor activities such as hiking and hot springs.
  • C. Ishkashimi
    Ishkashimi is a lesser-known Eastern Iranian language spoken by small communities in parts of Afghanistan and Tajikistan.
  • D. 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.
  • E. Hakatajima
    Hakatajima is an island in Japan’s Seto Inland Sea, known as one of the key islands linked by bridges along the scenic Shimanami Kaido cycling route between Honshu and Shikoku.
  • 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_69bd4419393c819086319a6fe4bf8542 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd71f555b48190984ee914ba1a91ee completed March 20, 2026, 4:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1132b29ac819086654ae935e819ef completed March 23, 2026, 10:17 a.m.
Created at: March 20, 2026, 1:32 p.m.