Triple
T15313558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRISPR-Cas9 gene-editing technology |
E366097
|
entity |
| Predicate | typicallyUsesPAM |
P118072
|
FINISHED |
| Object | NGG sequence for SpCas9 |
—
|
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: NGG sequence for SpCas9 | Statement: [CRISPR-Cas9 gene-editing technology, typicallyUsesPAM, NGG sequence for SpCas9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyUsesPAM Context triple: [CRISPR-Cas9 gene-editing technology, typicallyUsesPAM, NGG sequence for SpCas9]
-
A.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
-
B.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
C.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
D.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
-
E.
usedAsPatronOf
Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd050108190a584543cb93943a4 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.