Triple
T18784155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | phiC31 integrase system |
E459330
|
entity |
| Predicate | hasEngineeringVariant |
P455
|
FINISHED |
| Object | codon-optimized phiC31 integrase for mammalian expression |
—
|
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: codon-optimized phiC31 integrase for mammalian expression | Statement: [phiC31 integrase system, hasEngineeringVariant, codon-optimized phiC31 integrase for mammalian expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringVariant Context triple: [phiC31 integrase system, hasEngineeringVariant, codon-optimized phiC31 integrase for mammalian expression]
-
A.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
C.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
D.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
E.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977ffa648190be5f682bba47fb0a |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.