Triple
T18261023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muggle |
E437353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | term in the Harry Potter series |
C18005
|
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: term in the Harry Potter series Context triple: [Muggle, instanceOf, term in the Harry Potter series]
-
A.
Harry Potter character
chosen
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.
position in the Harry Potter universe
A position in the Harry Potter universe represents a specific role, job, or office held by a character within magical institutions, organizations, or social structures, defining their responsibilities, authority, and social standing.
-
C.
Harry Potter collectible line
A Harry Potter collectible line is a themed series of officially licensed items—such as figures, replicas, apparel, and memorabilia—designed for fans to collect, display, and celebrate the Wizarding World franchise.
-
D.
Harry Potter attraction
A Harry Potter attraction is an immersive themed experience, such as a ride, show, or interactive environment, that brings the magical world of the Harry Potter franchise to life for visitors.
-
E.
character in the Twilight series
A character in the Twilight series is an individual—human, vampire, or werewolf—whose personal history, supernatural traits, and relationships drive the romantic and dramatic conflicts within Stephenie Meyer’s Twilight universe.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.