Triple
T10214795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYP3A4 |
E242412
|
entity |
| Predicate | polymorphic |
P92783
|
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: [CYP3A4, polymorphic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polymorphic Context triple: [CYP3A4, polymorphic, true]
-
A.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
B.
multiplicity
Indicates the number of instances of one entity that can or must be associated with a single instance of another entity within a relationship.
-
C.
polyphony
Indicates a relationship where multiple independent melodic or vocal lines occur simultaneously, creating a layered or harmonically interwoven texture.
-
D.
polyalphabetic
Indicates that the relationship or action involves using multiple substitution alphabets or shifting schemes rather than a single, fixed mapping.
-
E.
predicate
Indicates that a specified relationship or action holds between given entities, without specifying its particular nature.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa273bdc8190bc4cf67a7923cebc |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11:04 a.m.