Triple

T11841647
Position Surface form Disambiguated ID Type / Status
Subject Ōkimi E281665 entity
Predicate authorityOver P1330 FINISHED
Object Yamato territory E299667 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: Yamato territory | Statement: [Ōkimi, authorityOver, Yamato territory]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yamato territory
Context triple: [Ōkimi, authorityOver, Yamato territory]
  • A. Yamato region
    The Yamato region is the early political and cultural heartland of Japan, where the first unified Japanese state emerged under the Yamato court.
  • B. Yamato area chosen
    The Yamato area is a historic cultural region in Nara Prefecture regarded as the cradle of early Japanese civilization and state formation.
  • C. Onekotan
    Onekotan is a remote volcanic island in Russia's Kuril Islands chain, known for its dramatic caldera lakes and rugged, uninhabited landscape.
  • D. Honshu
    Honshu is the largest and most populous island of Japan, home to major cities such as Tokyo, Osaka, and Kyoto.
  • E. Nan’yō Chō
    Nan’yō Chō was the Japanese colonial administration that governed the South Seas Mandate islands in the Pacific during the early 20th century.
  • 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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a658f918819092c2db05fe2ab0ce completed April 10, 2026, 7:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69f1678668ac81909bddf67e8c176757 completed April 29, 2026, 2:05 a.m.
Created at: April 8, 2026, 9:43 p.m.