Triple

T19824383
Position Surface form Disambiguated ID Type / Status
Subject Iwakura Ushijima E476280 entity
Predicate givenName P17 FINISHED
Object Iwakura 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: Iwakura | Statement: [Iwakura Ushijima, givenName, Iwakura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iwakura
Context triple: [Iwakura Ushijima, givenName, Iwakura]
  • A. Iwakura chosen
    Iwakura is a Japanese surname most famously associated with Iwakura Tomomi, a key statesman of the Meiji Restoration.
  • B. Ogizawa
    Ogizawa is a mountain gateway village in Nagano Prefecture, Japan, best known as an access point to the Tateyama Kurobe Alpine Route and the Kurobe Dam.
  • C. Isehara
    Isehara is a city in Kanagawa Prefecture, Japan, known as a residential and industrial area with access to nearby natural attractions such as the Tanzawa Mountains.
  • D. Takamado
    Takamado is a Japanese imperial family name most prominently associated with the late Prince Takamado and his descendants, a branch of Japan’s royal household.
  • E. Ichikawa
    Ichikawa is a city in Chiba Prefecture, Japan, located just east of Tokyo and known as a residential and commercial hub within the Greater Tokyo Area.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e655017c188190ae9e17ae6b0eee05 completed April 20, 2026, 4:32 p.m.
Created at: April 10, 2026, 1:50 p.m.