Triple
T22692125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanger sequencing |
E561076
|
entity |
| Predicate | lowerThroughputThan |
P141976
|
FINISHED |
| Object | next-generation sequencing |
—
|
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: next-generation sequencing | Statement: [Sanger sequencing, lowerThroughputThan, next-generation sequencing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerThroughputThan Context triple: [Sanger sequencing, lowerThroughputThan, next-generation sequencing]
-
A.
hasLowerThroughputThan
chosen
Indicates that one entity’s throughput is less than that of another entity.
-
B.
hasHigherThroughputThan
Indicates that one entity can process or transmit a greater volume of work, data, or operations per unit time than another entity.
-
C.
slowerThan
Indicates that one entity moves or operates at a lower speed than another entity.
-
D.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
E.
hasLowerColumnDensityLimitThan
Indicates that the column density of one entity is constrained to be lower than the column density of 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.