Triple

T33790135
Position Surface form Disambiguated ID Type / Status
Subject Bluidy Clavers E865908 entity
Predicate givenBecauseOf P24494 FINISHED
Object brutal enforcement 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: brutal enforcement of royal authority | Statement: [Bluidy Clavers, givenBecauseOf, brutal enforcement of royal authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: givenBecauseOf
Context triple: [Bluidy Clavers, givenBecauseOf, brutal enforcement of royal authority]
  • A. givenWhen
    Indicates a conditional or contextual relationship where one event, state, or action occurs under the circumstance or time that another specified event, state, or action is given or takes place.
  • B. existsBecauseOf
    Indicates that one entity’s existence is caused, enabled, or brought about by another entity.
  • C. givenFor
    Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
  • D. statedReason chosen
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • E. causeOf
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • 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_69f3498f99f481909cb271f4965a7594 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc59518081908b0275f47721d561 completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 1:45 a.m.