Triple

T13494202
Position Surface form Disambiguated ID Type / Status
Subject Fujiwara no Tametoki E320716 entity
Predicate givenName P17 FINISHED
Object Tametoki E952756 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: Tametoki | Statement: [Fujiwara no Tametoki, givenName, Tametoki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tametoki
Context triple: [Fujiwara no Tametoki, givenName, Tametoki]
  • A. Tomigusuku
    Tomigusuku is a coastal city on Japan’s Okinawa Island known for its proximity to Naha and its blend of urban development with traditional Ryukyuan culture.
  • B. Ōtoku
    Ōtoku was a Japanese era name (nengō) of the late 11th century, used during the reign of Emperor Shirakawa.
  • C. Tokomaru
    Tokomaru is a traditional Māori voyaging canoe (waka) associated with the Ngāpuhi iwi (tribe) in Aotearoa New Zealand.
  • D. Michitaka chosen
    Michitaka is a Japanese given name that has been borne by various historical and contemporary figures.
  • E. Toramana
    Toramana was a prominent Huna ruler in early 6th-century northern India, known for his extensive military campaigns and significant role in weakening the Gupta Empire.
  • 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_69d807629d6c8190998f1b9bb12d2ed0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaf4da2c88190a867b53529d39545 completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69fba1b300888190980173b585b27d48 completed May 6, 2026, 8:16 p.m.
Created at: April 9, 2026, 9:43 p.m.