Triple
T36095697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumbledore family |
E1044051
|
entity |
| Predicate | bloodStatusContext |
P22696
|
FINISHED |
| Object | not explicitly defined in canon |
—
|
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: not explicitly defined in canon | Statement: [Dumbledore family, bloodStatusContext, not explicitly defined in canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodStatusContext Context triple: [Dumbledore family, bloodStatusContext, not explicitly defined in canon]
-
A.
bloodStatus
chosen
Indicates the classification of an entity based on the type or purity of its blood or lineage.
-
B.
bloodRageStatus
Indicates a temporary state in which an entity is overcome by extreme, often uncontrollable, rage or bloodlust.
-
C.
bloodStatusTargetOfPrejudice
Indicates that an entity is the target of prejudice or discrimination specifically because of its blood status.
-
D.
hasBlood
Indicates that one entity possesses or contains the blood of another entity.
-
E.
bloodUsedFor
Indicates that blood is utilized or applied for a particular purpose, function, or process.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.