Triple
T22692123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanger sequencing |
E561076
|
entity |
| Predicate | readLength |
P266
|
FINISHED |
| Object | approximately 500–1000 bases |
—
|
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: approximately 500–1000 bases | Statement: [Sanger sequencing, readLength, approximately 500–1000 bases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readLength Context triple: [Sanger sequencing, readLength, approximately 500–1000 bases]
-
A.
outputLength
Indicates the length or size of the result produced by a process, function, or operation.
-
B.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
C.
IVLength
Indicates the measured length of an intravenous (IV) line or catheter used in a medical context.
-
D.
lengthOverBuffers
Indicates that the length or size of something exceeds the capacity or number of its associated buffers.
-
E.
relativeLength
Indicates a comparative relationship between entities based on how long they are relative to one another.
- 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.