Triple
T33206078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pregnane X receptor |
E850015
|
entity |
| Predicate | activatedState |
P153946
|
FINISHED |
| Object | ligand-bound heterodimer with RXRα |
—
|
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: ligand-bound heterodimer with RXRα | Statement: [Pregnane X receptor, activatedState, ligand-bound heterodimer with RXRα]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatedState Context triple: [Pregnane X receptor, activatedState, ligand-bound heterodimer with RXRα]
-
A.
activationStatus
Indicates whether an entity is currently active, enabled, or in effect within a given context.
-
B.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified entity.
-
C.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
D.
activeWith
chosen
Indicates that an entity is currently engaged in or functioning together with another specified entity.
-
E.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:30 a.m.