Triple
T28639065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bludger |
E724869
|
entity |
| Predicate | appearsInWorkOfFiction |
P105687
|
FINISHED |
| Object | Quidditch |
—
|
NE NERFINISHED |
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: Quidditch | Statement: [Bludger, appearsInWorkOfFiction, Quidditch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInWorkOfFiction Context triple: [Bludger, appearsInWorkOfFiction, Quidditch]
-
A.
usedInFictionalWork
chosen
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
B.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
-
C.
worksWithInFiction
Indicates that two fictional characters are depicted as collaborating, interacting, or being associated with each other within a narrative work.
-
D.
fictionalCharacterPortrayedFromWorkBy
Indicates that a fictional character is depicted or portrayed in a work that was created by a specific author or creator.
-
E.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 4:42 a.m.