Triple
T34091792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2 muscarinic acetylcholine receptor |
E874316
|
entity |
| Predicate | receptorSubtype |
P178411
|
FINISHED |
| Object | M2 |
—
|
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: M2 | Statement: [M2 muscarinic acetylcholine receptor, receptorSubtype, M2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receptorSubtype Context triple: [M2 muscarinic acetylcholine receptor, receptorSubtype, M2]
-
A.
receptor
Indicates that one entity functions as a receptor for another, typically binding or receiving a signal, substance, or stimulus from it.
-
B.
receptorTypeInteractedWith
Indicates that one entity has interacted with, bound to, or otherwise engaged a specific type of receptor.
-
C.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
-
D.
receptorTypeAtEffector
Indicates that a specific type of receptor is present at, or associated with, a particular effector site or effector cell.
-
E.
receptorInput
Indicates that a receptor receives or is provided with an input signal or stimulus from another entity.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:52 a.m.