Triple

T883452
Position Surface form Disambiguated ID Type / Status
Subject William the Conqueror E19075 entity
Predicate justificationForClaim P11285 FINISHED
Object alleged promise by Edward the Confessor 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: alleged promise by Edward the Confessor | Statement: [William the Conqueror, justificationForClaim, alleged promise by Edward the Confessor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: justificationForClaim
Context triple: [William the Conqueror, justificationForClaim, alleged promise by Edward the Confessor]
  • A. justification chosen
    Indicates that one entity provides a reason, explanation, or supporting argument for the existence, validity, or appropriateness of another entity or claim.
  • B. mainClaim
    Indicates that one statement is presented as the central or primary assertion being made about a topic.
  • C. reasonWritten
    Indicates that one entity is the reason or motivation for which another entity was written or authored.
  • D. reasonForGrant
    Indicates the justification, purpose, or cause for which a grant is awarded or provided.
  • E. justified
    Indicates that an action, belief, or decision is supported by sufficient reasons or evidence to be considered reasonable or warranted.
  • 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_69a4939c32488190a7ccd41cf0abb22b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4accda4148190aa628dab14d7f5de completed March 1, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69a4aa8eca748190b58e0f08b30fba43 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.