Triple

T20631795
Position Surface form Disambiguated ID Type / Status
Subject Rufus Scrimgeour E506972 entity
Predicate relationshipWithHarryPotter P131072 FINISHED
Object strained 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: strained | Statement: [Rufus Scrimgeour, relationshipWithHarryPotter, strained]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipWithHarryPotter
Context triple: [Rufus Scrimgeour, relationshipWithHarryPotter, strained]
  • A. roleInHarryPotter
    Indicates that one entity has a specific role or character part within the Harry Potter series in relation to the other entity.
  • B. relationshipTypeWithRubeusHagrid
    Indicates the specific nature or category of the relationship an entity has with Rubeus Hagrid (e.g., friend, colleague, student, family).
  • C. relationshipToHarry chosen
    Indicates the specific type of relationship or connection that an entity has to Harry.
  • D. relationshipToMinervaMcGonagall
    Indicates the specific familial, social, or professional relationship that an entity has to Minerva McGonagall.
  • E. roleOfHarryVanda
    Indicates that the specified role or function is held or performed by Harry Vanda in relation to another entity or context.
  • 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6ad0b0508819093c62a4ceaf860ce completed April 20, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69e5a0155bd48190b3c769a12cc2c83d completed April 20, 2026, 3:40 a.m.
Created at: April 16, 2026, 11:42 a.m.