Triple

T12878169
Position Surface form Disambiguated ID Type / Status
Subject Fushimi-no-miya head E308017 entity
Predicate familyName P18 FINISHED
Object Fushimi E287226 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: Fushimi | Statement: [Fushimi-no-miya head, familyName, Fushimi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fushimi
Context triple: [Fushimi-no-miya head, familyName, Fushimi]
  • A. Fushimi chosen
    Fushimi is a historic district in Kyoto, Japan, known for its castle and its association with key events and figures of the late Sengoku period.
  • B. Komagome
    Komagome is a residential and commercial neighborhood in Tokyo known for its traditional atmosphere, historic temples, and the renowned Rikugien Garden.
  • C. Toyonaka
    Toyonaka is a suburban city in Japan’s Kansai region known for its residential neighborhoods, educational institutions, and proximity to central Osaka.
  • D. Ueno
    Ueno is a major district in Tokyo known for Ueno Park, its museums, zoo, and busy transportation hub.
  • E. Ueno
    Ueno is a town in Japan historically known as the birthplace of the renowned haiku poet Matsuo Bashō.
  • 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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d970fa8474819086a8af3c90f3ca84 completed April 10, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb6b97888190923ce7a6e59ff752 completed May 8, 2026, 3:04 p.m.
Created at: April 9, 2026, 5:38 p.m.