Triple

T33784489
Position Surface form Disambiguated ID Type / Status
Subject Familia E865749 entity
Predicate positionOnCentralPower P22876 FINISHED
Object strengthening of royal 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: strengthening of royal authority | Statement: [Familia, positionOnCentralPower, strengthening of royal authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionOnCentralPower
Context triple: [Familia, positionOnCentralPower, strengthening of royal authority]
  • A. positionOnStatePower
    Indicates a stance or viewpoint an entity holds regarding the nature, scope, or use of state power.
  • B. mainCentralPower
    Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
  • C. positionOnCentralization chosen
    Indicates the degree to which an entity favors centralized versus decentralized control, authority, or decision-making.
  • D. positionRelativeToPower
    Indicates the spatial or structural placement of one entity in relation to a power source, power line, or power-related infrastructure.
  • E. powerLocation
    Indicates that an entity’s power, authority, or influence is situated in, originates from, or is exercised within a particular location.
  • 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_69f3498ecc2c8190bcd85e3f11dc215e completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff3b32ee148190a3ba3b7600943fef completed May 9, 2026, 1:48 p.m.
PD Predicate disambiguation batch_69ff3a238af88190a2c2245e30299e48 completed May 9, 2026, 1:44 p.m.
Created at: May 1, 2026, 1:45 a.m.