Triple
T22690382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IL-17A |
E561033
|
entity |
| Predicate | downregulatedBy |
P149277
|
FINISHED |
| Object | IL-27 |
—
|
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: IL-27 | Statement: [IL-17A, downregulatedBy, IL-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downregulatedBy Context triple: [IL-17A, downregulatedBy, IL-27]
-
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.
decreedBy
Indicates that something (such as a rule, decision, or order) has been formally established or mandated by a particular authority or decision-making entity.
-
C.
demotes
Indicates that one entity reduces another entity’s rank, status, or level within a hierarchy or system.
-
D.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
E.
cutDown
Indicates that an agent causes something standing or elevated (such as a tree or structure) to fall or be reduced by cutting.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789a1fd08190bce5fa0babe695d3 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:13 p.m.