Triple
T29181101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Technology Attachment |
E739745
|
entity |
| Predicate | transferRateRange |
P110272
|
FINISHED |
| Object | from a few MB/s up to 133 MB/s |
—
|
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: from a few MB/s up to 133 MB/s | Statement: [Advanced Technology Attachment, transferRateRange, from a few MB/s up to 133 MB/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferRateRange Context triple: [Advanced Technology Attachment, transferRateRange, from a few MB/s up to 133 MB/s]
-
A.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
bitrateRange
chosen
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
C.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
D.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
E.
bandwidthUnit
Indicates the unit of measurement used to express a given bandwidth value in the relationship.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 11:57 a.m.