Triple

T38151011
Position Surface form Disambiguated ID Type / Status
Subject Ryakuō E952750 entity
Predicate sovereignInNorthernCourt P190258 FINISHED
Object Emperor Kōmyō 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: Emperor Kōmyō | Statement: [Ryakuō, sovereignInNorthernCourt, Emperor Kōmyō]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sovereignInNorthernCourt
Context triple: [Ryakuō, sovereignInNorthernCourt, Emperor Kōmyō]
  • A. sovereignInRightOf
    Indicates that one entity holds sovereign authority or governing rights specifically in virtue of, or on behalf of, another entity (such as a state, territory, or crown).
  • B. sovereignInvolved
    Indicates that a sovereign authority (such as a monarch or state) is directly involved in, participates in, or is otherwise a key party to the referenced action or relationship.
  • C. nobleJurisdiction
    Indicates that an entity holds legal or administrative authority associated with nobility over a certain domain or group.
  • D. courtRegent
    Indicates that one entity serves as a regent or ruling authority within the court of another entity.
  • E. courtOf
    Indicates that one entity serves as the judicial body or tribunal associated with, or having jurisdiction over, another entity.
  • 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_69f76f0a67f4819080c492f61d688fcc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcc42cbac48190b8d3e4c9ce140838 completed May 7, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69fcb0fc69c88190800453eb57a7e62c completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc42b9334819099929649b7ef68ea completed May 7, 2026, 4:56 p.m.
Created at: May 3, 2026, 4:21 p.m.