Triple
T33206104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | constitutive androstane receptor |
E850016
|
entity |
| Predicate | expressedInSpecies |
P176411
|
FINISHED |
| Object | Homo sapiens |
—
|
NE NERFINISHED |
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: Homo sapiens | Statement: [constitutive androstane receptor, expressedInSpecies, Homo sapiens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressedInSpecies Context triple: [constitutive androstane receptor, expressedInSpecies, Homo sapiens]
-
A.
studiedInSpecies
Indicates that a particular study, observation, or experiment was conducted using or within the specified species.
-
B.
usedBySpecies
Indicates that something (such as an object, resource, or method) is utilized or employed by a particular species.
-
C.
measuredSpecies
Indicates that a particular species is the subject or target of a measurement or observation in a given context.
-
D.
geneticSpecies
Indicates that two entities share the same biological species based on their genetic characteristics.
-
E.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:30 a.m.