Triple
T6959775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaper strain vampires |
E161340
|
entity |
| Predicate | biologicalType |
P37835
|
FINISHED |
| Object | mutated vampire |
—
|
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: mutated vampire | Statement: [Reaper strain vampires, biologicalType, mutated vampire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biologicalType Context triple: [Reaper strain vampires, biologicalType, mutated vampire]
-
A.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
B.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
C.
organismType
chosen
Indicates the biological classification or kind of organism that an entity is.
-
D.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
-
E.
biologicalEvent
Indicates a relationship where an entity participates in, causes, or is affected by a process or occurrence in a biological system.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daedbb4c8190b46846fb1265b937 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.