Triple

T38345639
Position Surface form Disambiguated ID Type / Status
Subject shogun E1041531 entity
Predicate heldDeFactoPowerInsteadOf P131608 FINISHED
Object emperor of 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: emperor of Japan | Statement: [shogun, heldDeFactoPowerInsteadOf, emperor of Japan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldDeFactoPowerInsteadOf
Context triple: [shogun, heldDeFactoPowerInsteadOf, emperor of Japan]
  • A. heldExecutivePowerUntil
    Indicates that an entity exercised executive authority or leadership in a role or office up to a specified end date or point in time.
  • B. ruledInPlaceOf chosen
    Indicates that one entity exercised governing authority or leadership as a substitute or proxy for another entity.
  • C. hadExecutivePowerIn
    Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
  • D. reignAsDeFactoRulerEnd
    Indicates the point in time or event at which an entity’s period of exercising actual (but not officially recognized) ruling authority comes to an end.
  • E. cameToPowerAfter
    Indicates that one entity assumed authority or control following the rule or tenure of another entity.
  • 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_69f76e2ad95481908c920c0e5c1c3e26 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fcc7a4d7f881908b43b960911b81e9 completed May 7, 2026, 5:11 p.m.
PD Predicate disambiguation batch_69fcc589720c819089c8f500fea3c86a completed May 7, 2026, 5:02 p.m.
Created at: May 3, 2026, 4:30 p.m.