Triple
T36413360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagini Horcrux |
E896939
|
entity |
| Predicate | finalHorcruxesGroup |
P198248
|
FINISHED |
| Object | last two Horcruxes along with Harry Potter |
—
|
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: last two Horcruxes along with Harry Potter | Statement: [Nagini Horcrux, finalHorcruxesGroup, last two Horcruxes along with Harry Potter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalHorcruxesGroup Context triple: [Nagini Horcrux, finalHorcruxesGroup, last two Horcruxes along with Harry Potter]
-
A.
numberOfHorcruxes
Indicates the quantity of Horcruxes associated with a given entity.
-
B.
horcruxDestroyedBy
Indicates that a specific Horcrux is destroyed through the actions or intervention of a particular agent or method.
-
C.
horcrux
Indicates that an entity has created, contains, or is being used as a vessel to anchor and preserve another entity’s soul or life essence.
-
D.
creatorOfHorcrux
Indicates that one entity is the maker or originator of a particular Horcrux associated with another entity.
-
E.
diademHorcruxCreator
Indicates that the subject is the creator of the Horcrux associated with the diadem.
- F. None of above. chosen
Provenance (4 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_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
| PDg | Predicate description generation | batch_69fed48c92ec8190b3be88880d86de86 |
completed | May 9, 2026, 6:30 a.m. |
Created at: May 3, 2026, 4:10 p.m.