Triple

T38151043
Position Surface form Disambiguated ID Type / Status
Subject Nanboku-chō period E952751 entity
Predicate deFactoRulingPower P66131 FINISHED
Object Ashikaga shogunate 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: Ashikaga shogunate | Statement: [Nanboku-chō period, deFactoRulingPower, Ashikaga shogunate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deFactoRulingPower
Context triple: [Nanboku-chō period, deFactoRulingPower, Ashikaga shogunate]
  • A. deFactoPowerHolder chosen
    Indicates that an entity is the one effectively exercising power or control in practice, regardless of formal or legal authority.
  • B. hasRulingPeople
    Indicates that a group or entity serves as the governing or ruling authority over another entity.
  • C. deFactoHeadOfStateOf
    Indicates that one entity serves as the actual, effective head of state of another entity, regardless of whether this role is held officially or formally.
  • D. ruledUnderPolity
    Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
  • E. hasRulingPowers
    Indicates that an entity possesses authority or power to make and enforce rules, judgments, or decisions over others.
  • F. None of above.

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_69f76f0a67f4819080c492f61d688fcc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fccbd826708190b5fab12c4236299a completed May 7, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69fcc58838e08190b8fa54aa5c165f2d completed May 7, 2026, 5:02 p.m.
Created at: May 3, 2026, 4:21 p.m.