Triple

T913791
Position Surface form Disambiguated ID Type / Status
Subject Bourbon Reforms E19722 entity
Predicate increasedPowerOf P13002 FINISHED
Object peninsular officials 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: peninsular officials | Statement: [Bourbon Reforms, increasedPowerOf, peninsular officials]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: increasedPowerOf
Context triple: [Bourbon Reforms, increasedPowerOf, peninsular officials]
  • A. powerBy
    Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
  • B. regainedPowerIn
    Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
  • C. inPower
    Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
  • D. strengthensFrom chosen
    Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
  • E. exclusivePower
    Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
  • 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_69a4939f91a08190ba68c2c81eab90fe completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b6755c488190b7f7848110e3ea2c completed March 1, 2026, 9:58 p.m.
PD Predicate disambiguation batch_69a4b292d3408190947cbc2f794cf8c5 completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:39 p.m.