Triple

T14625417
Position Surface form Disambiguated ID Type / Status
Subject Fuchū E343330 entity
Predicate neighboringMunicipality P17964 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: [Fuchū, neighboringMunicipality, Kunitachi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kunitachi
Context triple: [Fuchū, neighboringMunicipality, 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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb46a4a9081908472b0a542028a7f completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf078c1248190889ce04cffbf51dc completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:26 a.m.