Triple
T36412983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyages with Vampires |
E896930
|
entity |
| Predicate | usedInClass |
P95791
|
FINISHED |
| Object | Defence Against the Dark Arts |
—
|
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: Defence Against the Dark Arts | Statement: [Voyages with Vampires, usedInClass, Defence Against the Dark Arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInClass Context triple: [Voyages with Vampires, usedInClass, Defence Against the Dark Arts]
-
A.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
B.
usedByClass
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
E.
availableInClass
chosen
Indicates that something can be accessed, used, or is valid within the scope of a particular class.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:10 p.m.