Triple

T14609300
Position Surface form Disambiguated ID Type / Status
Subject Christ Church, Yokohama E342913 entity
Predicate locatedInDistrict P40 FINISHED
Object Yamate E68433 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: Yamate | Statement: [Christ Church, Yokohama, locatedInDistrict, Yamate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yamate
Context triple: [Christ Church, Yokohama, locatedInDistrict, Yamate]
  • A. Yamate chosen
    Yamate is a historic hillside district in Yokohama known for its Western-style residences, foreign settlers’ heritage, and scenic views over the city and harbor.
  • B. Shimotsuki
    Shimotsuki was a Japanese destroyer of the Imperial Japanese Navy that served in World War II before being sunk in late 1944.
  • C. Irai
    Irai is a small commune in northern France, located within the Eure department in the Normandy region.
  • D. Yama
    Yama is the Hindu god of death and justice, traditionally regarded as the ruler of the afterlife and judge of the souls of the dead.
  • E. Yama
    Yama is the historical name of the Russian town now known as Kingisepp, located in Leningrad Oblast near the border with Estonia.
  • 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_69d822dec68081908c2553145c4051dc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb44f0dd48190a78662b5998a6722 completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fde16c005c81908b54fcfd4243d820 completed May 8, 2026, 1:13 p.m.
Created at: April 10, 2026, 1:25 a.m.