Triple
T25286362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reapers (Blade universe) |
E633950
|
entity |
| Predicate | heartProtection |
P158346
|
FINISHED |
| Object | bone-like cage around heart |
—
|
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: bone-like cage around heart | Statement: [Reapers (Blade universe), heartProtection, bone-like cage around heart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartProtection Context triple: [Reapers (Blade universe), heartProtection, bone-like cage around heart]
-
A.
heartColor
Indicates the color attribute associated with a heart.
-
B.
heartStructure
Indicates that one entity is a structural component, region, or anatomical feature of the heart of another entity.
-
C.
heartPresence
Indicates the existence or presence of a heart in or associated with the referenced entity.
-
D.
heartArrangement
Indicates how the components or structures of a heart are organized or positioned relative to one another.
-
E.
heartSymbol2
Indicates a relationship where one entity expresses affection, love, or strong positive emotion toward another, often symbolized by a heart icon or shape.
- 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_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_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:19 p.m.