Triple

T938019
Position Surface form Disambiguated ID Type / Status
Subject Princess Kazuko E20240 entity
Predicate ethnicGroup P194 FINISHED
Object Yamato Japanese E9573 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: Yamato Japanese | Statement: [Princess Kazuko, ethnicGroup, Yamato Japanese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yamato Japanese
Context triple: [Princess Kazuko, ethnicGroup, Yamato Japanese]
  • A. House of Yamato chosen
    The House of Yamato is Japan’s imperial dynasty, traditionally regarded as the world’s oldest continuing hereditary monarchy.
  • B. Yamato
    Yamato was a World War II-era Japanese battleship, famed as one of the largest and most heavily armed battleships ever constructed.
  • C. Yamamoto
    Yamamoto is a Japanese surname most famously associated with Admiral Isoroku Yamamoto, the commander-in-chief of the Imperial Japanese Navy during World War II.
  • D. Yapese
    Yapese is an Austronesian language spoken primarily on the island of Yap and nearby islands in the western Pacific.
  • E. Musashi
    Musashi was a World War II-era Japanese battleship, one of the largest and most heavily armed ever built, serving as a flagship of the Imperial Japanese Navy before being sunk in the Battle of Leyte Gulf.
  • 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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b388f0bc8190a087222636135ba5 completed March 1, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69a826e0dd188190bf5776a6e4525fdd completed March 4, 2026, 12:34 p.m.
Created at: March 1, 2026, 7:40 p.m.