Triple

T20244935
Position Surface form Disambiguated ID Type / Status
Subject Ōkuma Shigenobu E498398 entity
Predicate familyName P18 FINISHED
Object Ōkuma 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: Ōkuma | Statement: [Ōkuma Shigenobu, familyName, Ōkuma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ōkuma
Context triple: [Ōkuma Shigenobu, familyName, Ōkuma]
  • A. Ōkuma chosen
    Ōkuma is a Japanese surname most famously associated with statesman and educator Ōkuma Shigenobu, a key figure in Japan’s Meiji-era modernization.
  • B. Zuihō
    Zuihō was a Japanese light aircraft carrier of the Imperial Japanese Navy that served in several Pacific War operations before being sunk in the Battle off Cape Engaño in 1944.
  • C. Yamato
    Yamato was a World War II-era Japanese battleship, famed as one of the largest and most heavily armed battleships ever constructed.
  • D. Yamato
    Yamato refers to the dominant historical ethnic group and cultural core of Japan, traditionally associated with the imperial lineage and Shinto deities such as Amaterasu.
  • E. Yamato
    Yamato is a suburban city in Japan’s Kantō region known for its residential neighborhoods and role as a commuter hub within Kanagawa Prefecture.
  • 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_69da6274c58c81909c646eabed6f4f30 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e673a10ab48190a408a5d2c2b0808b completed April 20, 2026, 6:42 p.m.
Created at: April 11, 2026, 11:40 p.m.