Triple

T20567165
Position Surface form Disambiguated ID Type / Status
Subject Fajia E504993 entity
Predicate viewOnRuler P140592 FINISHED
Object ruler should be authoritative but personally withdrawn 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: ruler should be authoritative but personally withdrawn | Statement: [Fajia, viewOnRuler, ruler should be authoritative but personally withdrawn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: viewOnRuler
Context triple: [Fajia, viewOnRuler, ruler should be authoritative but personally withdrawn]
  • A. peakUnderRuler
    Indicates that a peak (such as a mountain or summit) is located within the domain or territory governed by a particular ruler.
  • B. coRulerWith
    Indicates that two or more entities share ruling authority over the same domain or polity at the same time.
  • C. involvesRuler
    Indicates that the relationship or action includes or pertains to a ruler as a participating party.
  • D. currentRuler
    Indicates that one entity is the present reigning ruler or head of state of another entity (such as a country, region, or polity).
  • E. providedRulerFor
    Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
  • 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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a7a33f7c8190966da03528dfe8aa completed April 20, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69e59ff0116c8190a163ff28ed01430a completed April 20, 2026, 3:39 a.m.
PDg Predicate description generation batch_69e5a6a824748190bbe6192d73f3c613 completed April 20, 2026, 4:08 a.m.
Created at: April 16, 2026, 11:39 a.m.