Triple
T25286331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reapers (Blade universe) |
E633950
|
entity |
| Predicate | mutationCause |
P68687
|
FINISHED |
| Object | vampire experimentation |
—
|
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: vampire experimentation | Statement: [Reapers (Blade universe), mutationCause, vampire experimentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutationCause Context triple: [Reapers (Blade universe), mutationCause, vampire experimentation]
-
A.
mutationType
Indicates the specific kind or category of genetic alteration that has occurred in an entity.
-
B.
mutationAssociatedWith
chosen
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
-
C.
secondaryMutation
Indicates that an additional, subsequent genetic alteration has occurred following an initial mutation in the same biological context.
-
D.
migrationCause
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
-
E.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0921ac8190a4a8fec7be7ad8f6 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:19 p.m.