Triple

T4254721
Position Surface form Disambiguated ID Type / Status
Subject Taira no Kiyomori E95944 entity
Predicate familyName P18 FINISHED
Object Taira E325846 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: Taira | Statement: [Taira no Kiyomori, familyName, Taira]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taira
Context triple: [Taira no Kiyomori, familyName, Taira]
  • A. Arinori
    Arinori was a given name of Mori Arinori, a prominent Meiji-era Japanese statesman and reformer known for modernizing Japan’s education system.
  • B. Taira clan chosen
    The Taira clan was a powerful samurai family that dominated late Heian-period Japanese court politics and warfare, ultimately clashing with rival Minamoto forces in the Genpei War.
  • C. Enryaku
    Enryaku was a Japanese era during the reign of Emperor Kanmu, notable for major political reforms and the early development of Kyoto as the imperial capital.
  • D. Seishirō
    Seishirō is a Japanese given name commonly used for male individuals.
  • E. Takayoshi
    Takayoshi is a Japanese given name notably borne by Kido Takayoshi, a key samurai and statesman of the Meiji Restoration.
  • 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_69b3453f759881909b91f01a1e82c036 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34ec036e8819087d8585170707545 completed March 12, 2026, 11:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5d06299288190bbd8e5f2cfd678d3 completed March 14, 2026, 9:17 p.m.
Created at: March 12, 2026, 11:06 p.m.