Triple
T20211190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts High Inquisitor |
E493489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional government office |
C40766
|
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: fictional government office Context triple: [Hogwarts High Inquisitor, instanceOf, fictional government office]
-
A.
fictional government ministry
A fictional government ministry is an imagined official department within a government, created in stories or worldbuilding to oversee specific policy areas, functions, or societal needs.
-
B.
fictional political institution
chosen
A fictional political institution is an imagined organization or governing body within a narrative world that creates, interprets, or enforces rules, policies, or power structures for story purposes.
-
C.
fictional judicial office
A fictional judicial office is an invented role or institution within an imagined legal system, endowed with specific authorities, procedures, and symbolic functions that shape how justice operates in that fictional world.
-
D.
fictional research institution
A fictional research institution is an imagined organization dedicated to conducting systematic investigation and experimentation, often serving as a setting or driver for scientific, technological, or societal developments within a narrative.
-
E.
fictional interstellar government
A fictional interstellar government is a large-scale political organization that exerts authority, creates laws, and manages relations across multiple planets, star systems, or galaxies within a speculative 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:38 p.m.