Triple
T10214791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYP3A4 |
E242412
|
entity |
| Predicate | enzymeCommissionNumber |
P92782
|
FINISHED |
| Object | EC 1.14.14.1 |
—
|
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: EC 1.14.14.1 | Statement: [CYP3A4, enzymeCommissionNumber, EC 1.14.14.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enzymeCommissionNumber Context triple: [CYP3A4, enzymeCommissionNumber, EC 1.14.14.1]
-
A.
commissionCommonName
Indicates that an entity is commonly known or referred to by a particular commission-related name.
-
B.
commissionedBy
Indicates that one entity has been formally requested, authorized, or hired by another entity to create, perform, or carry out something.
-
C.
commissionsAs
Indicates that one entity formally authorizes or hires another entity to create, perform, or carry out a specific work, task, or service.
-
D.
commissionYear
Indicates the year in which something (such as a work, project, or asset) was formally commissioned or authorized to be created or undertaken.
-
E.
numberOfCommissioners
Indicates the specific count of commissioners associated with a given entity or context.
- 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.