Triple
T36599206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAPK signaling pathway |
E902874
|
entity |
| Predicate | transmitsSignalFrom |
P58684
|
FINISHED |
| Object | cell surface receptors |
—
|
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: cell surface receptors | Statement: [MAPK signaling pathway, transmitsSignalFrom, cell surface receptors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmitsSignalFrom Context triple: [MAPK signaling pathway, transmitsSignalFrom, cell surface receptors]
-
A.
sentSignalFrom
chosen
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
B.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
C.
transmitsOn
Indicates that one entity sends or carries a signal, data, or content over a specified medium, channel, or frequency.
-
D.
transmitsVia
Indicates that something is conveyed, sent, or carried from one entity to another through a specified medium, channel, or mechanism.
-
E.
isTransmittedBy
Indicates that something (such as information, a signal, or a disease) is passed or conveyed from one entity to another through a specified agent or medium.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:11 p.m.