Triple

T2336485
Position Surface form Disambiguated ID Type / Status
Subject Yokosuka Naval Arsenal E44321 entity
Predicate locatedIn P40 FINISHED
Object Yokosuka E281970 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: Yokosuka | Statement: [Yokosuka Naval Arsenal, locatedIn, Yokosuka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yokosuka
Context triple: [Yokosuka Naval Arsenal, locatedIn, Yokosuka]
  • A. Yokosuka chosen
    Yokosuka is a coastal city in Kanagawa Prefecture, Japan, known for its major naval base and strategic location at the mouth of Tokyo Bay.
  • B. Tachikawa
    Tachikawa is a major city in western Tokyo, Japan, known as a key commercial and transportation hub of the Tama region.
  • C. Kawanishi
    Kawanishi is a city in Hyōgo Prefecture, Japan, known as a residential and commuter town within the Osaka metropolitan area.
  • D. Yawata
    Yawata is a city in Japan known for its historic Iwashimizu Hachimangū Shrine and its location in the southern part of Kyoto Prefecture.
  • E. Shizuoka
    Shizuoka is a coastal city in central Japan known for its views of Mount Fuji, green tea production, and role as the capital of Shizuoka Prefecture.
  • 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_69a889132b488190bbb43ad4780ddd92 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abc68927988190888630b5fa8f91dd completed March 7, 2026, 6:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69afaf2c245c8190a426cfcdc929efeb completed March 10, 2026, 5:42 a.m.
Created at: March 4, 2026, 7:51 p.m.