Triple

T11622937
Position Surface form Disambiguated ID Type / Status
Subject Tadahiko Taira E276185 entity
Predicate givenName P17 FINISHED
Object Tadahiko E276185 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: Tadahiko | Statement: [Tadahiko Taira, givenName, Tadahiko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tadahiko
Context triple: [Tadahiko Taira, givenName, Tadahiko]
  • A. Tadahiko chosen
    Tadahiko is a Japanese masculine given name used by various notable individuals in fields such as sports, arts, and academia.
  • B. Yasuhiko
    Yasuhiko is a Japanese given name notably borne by Prince Asaka Yasuhiko, a member of the Imperial Family of Japan in the early 20th century.
  • C. Toshiaki
    Toshiaki is a Japanese masculine given name commonly used for men and boys in Japan.
  • D. Tetsuzō
    Tetsuzō is an alternate name for Katsushika Hokusai, the renowned Japanese ukiyo-e artist best known for his woodblock print series "Thirty-Six Views of Mount Fuji."
  • E. Yasuhiro
    Yasuhiro is a Japanese masculine given name borne by various notable figures in politics, sports, and entertainment.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a122a3708190ab6513dad4c4fde7 completed April 10, 2026, 7:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69f61e33557c8190a724bb45c59abc63 completed May 2, 2026, 3:54 p.m.
Created at: April 8, 2026, 9:39 p.m.