Triple
T20210791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horcrux |
E493480
|
entity |
| Predicate | requiresForCreation |
P98983
|
FINISHED |
| Object | Deliberate act of murder |
—
|
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: Deliberate act of murder | Statement: [Horcrux, requiresForCreation, Deliberate act of murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresForCreation Context triple: [Horcrux, requiresForCreation, Deliberate act of murder]
-
A.
requiresPresence
Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
-
B.
requiresInitiationIn
chosen
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
-
C.
requiresLock
Indicates that performing the associated action or accessing the related resource is contingent on acquiring a lock to ensure exclusive or synchronized use.
-
D.
requiresRegistrationFor
Indicates that one entity can only access, use, or participate in another entity if a prior registration process has been completed.
-
E.
requiresForFeature
Indicates that one entity must be present, implemented, or satisfied in order for a particular feature of another entity to be available or function correctly.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed5691c8190bf253b1d4ee6e88f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.