Triple
T15564161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revio System |
E371072
|
entity |
| Predicate | supportsReadType |
P24486
|
FINISHED |
| Object | HiFi long reads |
—
|
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: HiFi long reads | Statement: [Revio System, supportsReadType, HiFi long reads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReadType Context triple: [Revio System, supportsReadType, HiFi long reads]
-
A.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
hasReadingType
Indicates that an entity is associated with a specific category or mode of reading, such as a particular interpretation, format, or type of reading measurement.
-
C.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
D.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
E.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddc66448190948280fb0c8d390c |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.