Triple

T22851688
Position Surface form Disambiguated ID Type / Status
Subject 和人 E566370 entity
Predicate 別名 P39 FINISHED
Object Wajin 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: Wajin | Statement: [和人, 別名, Wajin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wajin
Context triple: [和人, 別名, Wajin]
  • A. Wajin chosen
    Wajin is a historical term used in East Asia to refer to the ethnic Japanese people, particularly those of the Yamato cultural and political core.
  • B. Wako
    Wako is a suburban city in Saitama Prefecture, Japan, located on the northern outskirts of Tokyo and known as a residential and commuter hub.
  • C. Yamanakako
    Yamanakako is a village in Yamanashi Prefecture, Japan, known for Lake Yamanaka, one of the Fuji Five Lakes located near Mount Fuji.
  • D. Shobijin
    Shobijin are the tiny twin priestesses who serve as Mothra’s mystical spokespeople and guardians in the Godzilla and broader kaiju film universe.
  • E. Shizu
    Shizu is the posthumous temple name by which Emperor Guangwu, the restorer and founding ruler of the Eastern Han dynasty in China, is venerated in ancestral rites.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17eb9a5b8819091cbb4ac42fbf778 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.