Triple

T17807966
Position Surface form Disambiguated ID Type / Status
Subject Taira no Tokuko E444616 entity
Predicate familyName P18 FINISHED
Object Taira 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: Taira | Statement: [Taira no Tokuko, familyName, Taira]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taira
Context triple: [Taira no Tokuko, familyName, Taira]
  • A. Taira chosen
    Taira was a powerful samurai clan that dominated late Heian-period Japanese politics and warfare before its downfall in the Genpei War.
  • B. Soga
    Soga is a Bantu language spoken primarily in eastern Uganda by the Basoga people.
  • C. Mutsu
    Mutsu was a Japanese Nagato-class battleship of the Imperial Japanese Navy that served prominently during the interwar period and World War II before being destroyed by an internal explosion in 1943.
  • D. Mutsu
    Mutsu is a coastal city in northern Japan known for its proximity to the Shimokita Peninsula and natural hot springs.
  • E. Arinori
    Arinori was a given name of Mori Arinori, a prominent Meiji-era Japanese statesman and reformer known for modernizing Japan’s education system.
  • 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e488779a3081908405eac4930a095f completed April 19, 2026, 7:47 a.m.
Created at: April 10, 2026, 10:14 a.m.