Triple
T37350810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crouch family |
E927315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Harry Potter character group |
C55287
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Harry Potter character group Context triple: [Crouch family, instanceOf, Harry Potter character group]
-
A.
Harry Potter character
A Harry Potter character is an individual—human or magical creature—who exists within the Harry Potter universe, possessing distinct traits, roles, and relationships that contribute to the series’ narrative and world-building.
-
B.
Fantastic Beasts character
A Fantastic Beasts character is an individual—human or magical creature—who exists within the Wizarding World of the Fantastic Beasts film series, contributing to its narrative through their unique magical abilities, personal history, and relationships to the broader Harry Potter canon.
-
C.
wizarding group
chosen
A wizarding group is an organized association of magic users who collaborate to share knowledge, pursue common goals, and exercise influence within the magical world.
-
D.
object in the Harry Potter universe
A magical or mundane item that exists within the Harry Potter universe, often imbued with specific enchantments, rules, and narrative significance that influence characters and events.
-
E.
Hogwarts student
A Hogwarts student is a young witch or wizard enrolled at Hogwarts School of Witchcraft and Wizardry to study magical subjects, develop their abilities, and participate in the school's social and house-based activities.
- F. None of above.
Provenance (1 batch)
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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.