Triple

T20428150
Position Surface form Disambiguated ID Type / Status
Subject Committee for the Disposal of Dangerous Creatures E501057 entity
Predicate knownCase P7437 FINISHED
Object Buckbeak the hippogriff trial 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: Buckbeak the hippogriff trial | Statement: [Committee for the Disposal of Dangerous Creatures, knownCase, Buckbeak the hippogriff trial]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownCase
Context triple: [Committee for the Disposal of Dangerous Creatures, knownCase, Buckbeak the hippogriff trial]
  • A. hasCase chosen
    Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
  • B. knownForDecision
    Indicates that an entity is recognized or notable specifically for making a particular decision.
  • C. knownCasesLinked
    Indicates that multiple already-identified cases are connected or related to each other in some meaningful way (e.g., by source, pattern, or chain of events).
  • D. knownBefore
    Indicates that one entity had knowledge or awareness of another entity or event prior to a specified time or before another referenced event occurred.
  • E. knownResult
    Indicates that the outcome or consequence of an action, process, or event is already determined and available.
  • 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_69e0b4aa68fc8190b1a14c55575ef04a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67baa91b881909dfd68ccca25063c completed April 20, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69e5766df0008190a73c4f613c29678f completed April 20, 2026, 12:42 a.m.
Created at: April 16, 2026, 11:31 a.m.