Triple

T4796072
Position Surface form Disambiguated ID Type / Status
Subject Charter of 1814 E106713 entity
Predicate confersPowerOnMonarch P59315 FINISHED
Object executive authority 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: executive authority | Statement: [Charter of 1814, confersPowerOnMonarch, executive authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: confersPowerOnMonarch
Context triple: [Charter of 1814, confersPowerOnMonarch, executive authority]
  • A. monarchSheIsHeirTo
    Indicates that the subject is the designated heir to the specified monarch’s throne or title.
  • B. broughtToThroneBy
    Indicates that an individual attained a throne or royal position through the actions, support, or intervention of another party.
  • C. crownedAs
    Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
  • D. commandingMonarch
    Indicates that one entity is the ruling monarch who issues orders or exercises authoritative command over another entity.
  • E. regentOf
    Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
  • 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_69bd43f591c881909e5a532388b0f3f3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6b40c29c8190adab3503f8ba0145 completed March 20, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69bd622f88188190a51d52ccfad3d2dd completed March 20, 2026, 3:05 p.m.
PDg Predicate description generation batch_69bd6b3fb598819084a83d2b765a62b0 completed March 20, 2026, 3:43 p.m.
Created at: March 20, 2026, 1:22 p.m.