Triple
T32280222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American (wizarding world) |
E824668
|
entity |
| Predicate | usesTermForNonMagicalPeople |
P185232
|
FINISHED |
| Object | No-Maj |
—
|
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: No-Maj | Statement: [American (wizarding world), usesTermForNonMagicalPeople, No-Maj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTermForNonMagicalPeople Context triple: [American (wizarding world), usesTermForNonMagicalPeople, No-Maj]
-
A.
usesTermForMuggles
chosen
Indicates that one entity employs a particular term or expression to refer to non-magical people (muggles).
-
B.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
C.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
D.
knowsAboutMagic
Indicates that one entity possesses knowledge or awareness of magic in relation to another entity or context.
-
E.
languageOfIncantation
Indicates that a specified language is the one in which a particular incantation is spoken or written.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 12:43 a.m.