Triple

T13455874
Position Surface form Disambiguated ID Type / Status
Subject Feudal Japan E311229 entity
Predicate nominalRulerTitle P105547 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: [Feudal Japan, nominalRulerTitle, emperor of Japan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nominalRulerTitle
Context triple: [Feudal Japan, nominalRulerTitle, emperor of Japan]
  • A. traditionalRulerTitleInArea chosen
    Indicates that a specific traditional ruler’s title is officially recognized as holding authority within a particular geographic or administrative area.
  • B. rulerOf
    Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
  • C. involvesRuler
    Indicates that the relationship or action includes or pertains to a ruler as a participating party.
  • D. mainRuler
    Indicates that one entity is the primary sovereign or highest-ranking ruler over another entity, such as a territory, people, or political unit.
  • E. namedForTitle
    Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaefc52448190b30d7999f44a9765 completed April 12, 2026, 2:41 p.m.
PD Predicate disambiguation batch_69d9a03ce03481908c61094f0cc0c158 completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:41 p.m.