Triple
T33205448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tumor necrosis factor alpha |
E850005
|
entity |
| Predicate | cleavedBy |
P176187
|
FINISHED |
| Object | TACE |
—
|
NE NERFINISHED |
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: TACE | Statement: [tumor necrosis factor alpha, cleavedBy, TACE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleavedBy Context triple: [tumor necrosis factor alpha, cleavedBy, TACE]
-
A.
cleavagePattern
Indicates the characteristic way in which something splits, divides, or separates into parts under specific conditions.
-
B.
cleavageOrientation
Indicates the directional alignment or pattern along which a material or object tends to split or cleave.
-
C.
canBeDissectedBy
Indicates that one entity is capable of being divided or analyzed into parts by another entity or method.
-
D.
clearedOf
Indicates that an entity has been officially found not responsible for, or freed from suspicion of, a previously alleged wrongdoing, charge, or negative condition.
-
E.
cleared
Indicates that an entity has removed obstacles, doubts, or restrictions from another entity or from a particular state or situation.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.