Triple
T15564056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sequel System |
E371070
|
entity |
| Predicate | supportsChemistry |
P113995
|
FINISHED |
| Object | SMRTbell library preparation |
—
|
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: SMRTbell library preparation | Statement: [Sequel System, supportsChemistry, SMRTbell library preparation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChemistry Context triple: [Sequel System, supportsChemistry, SMRTbell library preparation]
-
A.
usesChemistry
chosen
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
-
B.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
-
C.
usedInChemistry
Indicates that something is employed or applied within the context of chemistry, such as in chemical processes, experiments, or analyses.
-
D.
containsChemical
Indicates that one entity includes or has within it a specified chemical substance.
-
E.
keyChemicalDiscussed
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddc66448190948280fb0c8d390c |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.