Triple

T20920356
Position Surface form Disambiguated ID Type / Status
Subject Bungo Province E515189 entity
Predicate hasNotablePort P6498 FINISHED
Object Usuki 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: Usuki | Statement: [Bungo Province, hasNotablePort, Usuki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Usuki
Context triple: [Bungo Province, hasNotablePort, Usuki]
  • A. Usuki chosen
    Usuki is a historic coastal city in Japan known for its well-preserved samurai district and famous stone Buddha statues.
  • B. Ebisu
    Ebisu is a fashionable Tokyo neighborhood known for its upscale dining, craft beer scene, and convenient access via Ebisu Station near Shibuya.
  • C. Ebisu
    Ebisu is a popular Japanese kami of prosperity, fishermen, and good fortune, often depicted as a cheerful, bearded man holding a fishing rod and sea bream.
  • D. Nisshu
    Nisshu was a Buddhist disciple of the Japanese monk Nichiren, known for helping to develop and spread Nichiren Buddhism.
  • E. Fusa
    Fusa is a village in Vestland county, Norway, known historically as the administrative center of the former Fusa Municipality.
  • 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_69e0b4f9d5ec8190bb2bd27350ed341c completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6ec677338819081410cbaa2846260 completed April 21, 2026, 3:17 a.m.
Created at: April 16, 2026, 12:48 p.m.