Triple
T33206101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | constitutive androstane receptor |
E850016
|
entity |
| Predicate | primarySiteOfExpression |
P203067
|
FINISHED |
| Object | liver |
—
|
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: liver | Statement: [constitutive androstane receptor, primarySiteOfExpression, liver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySiteOfExpression Context triple: [constitutive androstane receptor, primarySiteOfExpression, liver]
-
A.
primarySites
Indicates the main or originating locations associated with an entity, often distinguishing them from secondary or related sites.
-
B.
primaryRecordingSite
Indicates the main anatomical or spatial location where a recording or measurement was originally captured.
-
C.
primaryTranscript
Indicates that one entity is the initial RNA transcript directly produced from the transcription of another entity’s DNA sequence, prior to any RNA processing.
-
D.
expressedOn
Indicates that something (such as a feature, marker, or characteristic) is present or manifested on a particular entity or surface.
-
E.
primaryLocationIn
chosen
Indicates that an entity’s main or most significant location is within or at the referenced place.
- 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.