Triple
T5128387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remus Lupin |
E115635
|
entity |
| Predicate | causeOfLycanthropy |
P694
|
FINISHED |
| Object | bitten by Fenrir Greyback |
—
|
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: bitten by Fenrir Greyback | Statement: [Remus Lupin, causeOfLycanthropy, bitten by Fenrir Greyback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLycanthropy Context triple: [Remus Lupin, causeOfLycanthropy, bitten by Fenrir Greyback]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
viewpointOnWitchcraft
Indicates the stance, opinion, or perspective that an entity holds regarding witchcraft.
-
C.
causeOfVow
Indicates that one event, condition, or entity is the reason or motivating factor behind another entity making a vow.
-
D.
containsSupernaturalElement
Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
-
E.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.