Triple
T26136317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ion Torrent |
E659392
|
entity |
| Predicate | libraryPreparation |
P95223
|
FINISHED |
| Object | emulsion PCR on beads |
—
|
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: emulsion PCR on beads | Statement: [Ion Torrent, libraryPreparation, emulsion PCR on beads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: libraryPreparation Context triple: [Ion Torrent, libraryPreparation, emulsion PCR on beads]
-
A.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
B.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
C.
libraryDevelopment
Indicates the process or activity of planning, creating, expanding, or improving a library’s collections, services, or infrastructure.
-
D.
libraryUsed
Indicates that one entity makes use of another entity as a software or code library to provide functionality or services.
-
E.
preparesWith
chosen
Indicates that one entity is used as a means, tool, or method by which another entity is prepared or made ready.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b96c1ac8190adc0ceb44507777e |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:17 p.m.