Triple
T22692134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanger sequencing |
E561076
|
entity |
| Predicate | templateCanBe |
P107342
|
FINISHED |
| Object | PCR product |
—
|
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: PCR product | Statement: [Sanger sequencing, templateCanBe, PCR product]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templateCanBe Context triple: [Sanger sequencing, templateCanBe, PCR product]
-
A.
defaultTemplate
Indicates that something serves as the standard or pre-defined pattern or structure used when no specific alternative is chosen.
-
B.
قالب
Indicates a template or mold relationship, where one entity serves as a predefined pattern or structural format used to shape, generate, or standardize another entity.
-
C.
hasTemplate
chosen
Indicates that one entity uses, is based on, or is associated with a particular template defined by another entity.
-
D.
isTemplateBased
Indicates that one entity is derived from, structured according to, or instantiated using another entity as a template.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789ba0148190891781d05ec64f3c |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.