Triple

T28129206
Position Surface form Disambiguated ID Type / Status
Subject Minamoto no Yoshinaka E711014 entity
Predicate roleInGenpeiWar P195766 FINISHED
Object leader of Minamoto forces in central Japan LITERAL 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: leader of Minamoto forces in central Japan | Statement: [Minamoto no Yoshinaka, roleInGenpeiWar, leader of Minamoto forces in central Japan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInGenpeiWar
Context triple: [Minamoto no Yoshinaka, roleInGenpeiWar, leader of Minamoto forces in central Japan]
  • A. roleInShinKokinWakashu
    Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
  • B. roleInShu
    Indicates that an entity holds or plays a specific role within the context of Shu (e.g., the state, domain, or system referred to as Shu).
  • C. roleInAnime
    Indicates that an entity holds a specific character role or participation in a particular anime work.
  • D. roleInMonsterVerse
    Indicates that an entity has a specific role or function within the MonsterVerse franchise or universe.
  • E. roleInKojiki
    Indicates the role or function an entity holds within the narrative or structure of the Kojiki.
  • F. None of above. chosen

Provenance (4 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_69ef9b73bd288190a21ae3d6aa14f386 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69fde5d7d9548190880a9d95b8f0f66b completed May 8, 2026, 1:32 p.m.
PD Predicate disambiguation batch_69fde4e1bf9c81909754545275eccc03 completed May 8, 2026, 1:28 p.m.
PDg Predicate description generation batch_69fde5d677b88190bc904e6df8617c18 completed May 8, 2026, 1:32 p.m.
Created at: April 27, 2026, 9:22 p.m.