Triple
T10610110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rimonabant |
E275982
|
entity |
| Predicate | isHighlyProteinBound |
P37224
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [rimonabant, isHighlyProteinBound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighlyProteinBound Context triple: [rimonabant, isHighlyProteinBound, true]
-
A.
hasProteinBinding
chosen
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
-
B.
isHydrophobic
Indicates that one entity has a tendency to repel or avoid interaction with water or aqueous environments.
-
C.
hasBioavailability
Indicates that a substance has a specified degree or measure of bioavailability, i.e., the proportion that enters circulation and can have an active effect.
-
D.
isPegylated
Indicates that a molecule, typically a drug or therapeutic agent, has been chemically modified by the attachment of polyethylene glycol (PEG) chains.
-
E.
hasBindingEnergy
Indicates that one entity possesses or is characterized by a specific amount of binding energy associated with its formation or stability.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df59468881909b0c67d3f08c4b76 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:32 p.m.