Triple
T26136318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ion Torrent |
E659392
|
entity |
| Predicate | templateAttachment |
P159983
|
FINISHED |
| Object | DNA bound to beads loaded into wells |
—
|
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: DNA bound to beads loaded into wells | Statement: [Ion Torrent, templateAttachment, DNA bound to beads loaded into wells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templateAttachment Context triple: [Ion Torrent, templateAttachment, DNA bound to beads loaded into wells]
-
A.
attachmentType
Indicates the specific kind or category of attachment that relates one entity to another.
-
B.
supportsAttachmentTo
Indicates that one entity provides a structural or functional basis for another entity to be attached or affixed to it.
-
C.
supportsAttachments
Indicates that the subject is capable of handling or allowing the inclusion of file or data attachments in its operation or context.
-
D.
developsAttachmentTo
Indicates that one entity forms an emotional bond or sense of connection toward another entity.
-
E.
defaultTemplate
Indicates that something serves as the standard or pre-defined pattern or structure used when no specific alternative is chosen.
- 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_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. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:17 p.m.