Triple
T37724434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rat Cnr2 |
E939679
|
entity |
| Predicate | associatedProtein |
P149304
|
FINISHED |
| Object | CB2 |
—
|
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: CB2 | Statement: [rat Cnr2, associatedProtein, CB2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedProtein Context triple: [rat Cnr2, associatedProtein, CB2]
-
A.
proteinComplexAssociation
Indicates an association where multiple proteins interact to form or participate in a protein complex.
-
B.
targetsProtein
Indicates that one entity is directed toward, binds to, or is intended to affect a specific protein as its primary molecular target.
-
C.
functionallyRelatedTo
chosen
Indicates that two entities are connected through a functional relationship, where the operation, behavior, or role of one depends on, influences, or complements that of the other.
-
D.
hasProteinBinding
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
-
E.
uniprotId
Indicates that an entity is associated with a specific UniProt database identifier for a protein.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.