Triple

T17102375
Position Surface form Disambiguated ID Type / Status
Subject Tama area E415010 entity
Predicate hasPart P35 FINISHED
Object Kunitachi E241192 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: Kunitachi | Statement: [Tama area, hasPart, Kunitachi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kunitachi
Context triple: [Tama area, hasPart, Kunitachi]
  • A. Kunitachi chosen
    Kunitachi is a suburban city in western Tokyo, Japan, known for its universities, tree-lined avenues, and residential character.
  • B. Hidaka-hime
    Hidaka-hime is the birth name of Empress Genshō, a Nara-period Japanese empress who ruled in the early 8th century.
  • C. Asahi-hime
    Asahi-hime was a Japanese noblewoman of the late Sengoku period, known for her politically significant marriage into the Tokugawa clan that helped secure alliances during Japan’s unification.
  • D. Tsutako
    Tsutako is a Japanese given name, most notably borne by Tsutako Nakasone.
  • E. Yodo-dono
    Yodo-dono was a prominent Japanese noblewoman and political figure of the late Sengoku period, best known as Toyotomi Hideyoshi’s consort and the mother of his heir, Toyotomi Hideyori.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc239a088190a776fe0f4361ffc7 completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a031b10f34c81908bd52d2d581da69a completed May 12, 2026, 12:20 p.m.
Created at: April 10, 2026, 5:35 a.m.