Triple
T22692137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanger sequencing |
E561076
|
entity |
| Predicate | errorTypesInclude |
P144597
|
FINISHED |
| Object | base miscalls |
—
|
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: base miscalls | Statement: [Sanger sequencing, errorTypesInclude, base miscalls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorTypesInclude Context triple: [Sanger sequencing, errorTypesInclude, base miscalls]
-
A.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
B.
warningIncludes
Indicates that a warning message or notice contains or encompasses specific information, elements, or details.
-
C.
hasErrorType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of error.
-
D.
includesOffenseType
Indicates that one entity contains, specifies, or is associated with a particular category or type of offense.
-
E.
includesException
Indicates that one entity explicitly contains, references, or accounts for a specified exception within its definition, behavior, or processing.
- 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.