Triple
T33206133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | constitutive androstane receptor |
E850016
|
entity |
| Predicate | hasConstitutiveActivity |
P206384
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [constitutive androstane receptor, hasConstitutiveActivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstitutiveActivity Context triple: [constitutive androstane receptor, hasConstitutiveActivity, yes]
-
A.
hasActivityRegulation
Indicates that one entity exerts control over the level, timing, or manner of another entity’s activity.
-
B.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
hasActiveMetabolite
Indicates that a substance produces one or more metabolites that remain pharmacologically active in the body.
-
D.
hasEnzymeActivity
Indicates that an entity performs or exhibits a specific enzyme-catalyzed biochemical activity.
-
E.
hasNucleusActivity
Indicates that an entity performs, exhibits, or is involved in functional activity occurring within a nucleus.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:30 a.m.