Triple
T20211288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood quill |
E493491
|
entity |
| Predicate | fictionalObjectInUniverse |
P84710
|
FINISHED |
| Object | Harry Potter universe |
—
|
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: Harry Potter universe | Statement: [Blood quill, fictionalObjectInUniverse, Harry Potter universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalObjectInUniverse Context triple: [Blood quill, fictionalObjectInUniverse, Harry Potter universe]
-
A.
fictionalObject
chosen
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
B.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
C.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
D.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
E.
fictionalUniverseCreated
Indicates that one entity is the creator or originator of a particular fictional universe or setting in which stories or works take place.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed5691c8190bf253b1d4ee6e88f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.