Triple
T9807378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | programmed death-ligand 1 |
E238185
|
entity |
| Predicate | upregulatedBy |
P39508
|
FINISHED |
| Object | interferon-gamma |
—
|
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: interferon-gamma | Statement: [programmed death-ligand 1, upregulatedBy, interferon-gamma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upregulatedBy Context triple: [programmed death-ligand 1, upregulatedBy, interferon-gamma]
-
A.
developmentallyRegulatedBy
Indicates that the occurrence, level, or activity of one process or feature is controlled or influenced by developmental stage–specific mechanisms or factors.
-
B.
enhancedBy
chosen
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
C.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
D.
secretedInResponseTo
Indicates that a substance is released or discharged as a direct reaction to a specific stimulus, condition, or event.
-
E.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7ddaac8190a5584a5c863fbaa3 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.