Triple

T19639724
Position Surface form Disambiguated ID Type / Status
Subject Nagako E471498 entity
Predicate memberOf P10 FINISHED
Object House of Kuni 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: House of Kuni | Statement: [Nagako, memberOf, House of Kuni]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: House of Kuni
Context triple: [Nagako, memberOf, House of Kuni]
  • A. House of Kuni chosen
    The House of Kuni is a Japanese imperial noble family line to which Empress Kōjun belonged.
  • B. House of Ji
    The House of Ji was the hereditary ruling clan of the ancient Chinese State of Lu, traditionally associated with the lineage of the Zhou royal family.
  • C. House of Mi
    The House of Mi was the royal family clan that ruled the ancient Chinese state of Chu during the Zhou dynasty.
  • D. House of Asaka
    The House of Asaka was a collateral branch of Japan’s imperial family, founded by Prince Asaka Yasuhiko in the early 20th century.
  • E. House of Kuenring
    The House of Kuenring was a powerful medieval Austrian noble family that played a significant role in the political and military affairs of the Duchy of Austria.
  • 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_69d8e511f28481909f4bc3ea9191e54a completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e641215df48190926b38e6502bb83e completed April 20, 2026, 3:07 p.m.
Created at: April 10, 2026, 1:44 p.m.