Triple

T4419518
Position Surface form Disambiguated ID Type / Status
Subject Emperor Shirakawa E95062 entity
Predicate givenName P17 FINISHED
Object Sadahito E458183 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: Sadahito | Statement: [Emperor Shirakawa, givenName, Sadahito]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sadahito
Context triple: [Emperor Shirakawa, givenName, Sadahito]
  • A. Sadahito chosen
    Sadahito was the personal name of Emperor Shirakawa, a Japanese emperor of the late 11th and early 12th centuries known for initiating the cloistered rule system.
  • B. Yorihito
    Yorihito was a Japanese imperial prince of the Higashifushimi-no-miya house who served as a high-ranking naval officer during the late Meiji and Taishō periods.
  • C. Masaharu
    Masaharu is a Japanese masculine given name that can be written with various kanji combinations and is borne by several notable figures in Japanese history and culture.
  • D. Masaru
    Masaru is a Japanese given name commonly used for males and borne by various notable figures in fields such as technology, sports, and entertainment.
  • E. Shinpei
    Shinpei is a Japanese given name commonly used for males and borne by various notable figures in politics, arts, 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_69b3453a36908190b95a79a297ca083c completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3551fae7c8190abafda0d78f02d89 completed March 13, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69be03295174819096d299919a6d7e57 completed March 21, 2026, 2:32 a.m.
Created at: March 12, 2026, 11:29 p.m.