Triple
T8864863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATA-5 |
E210991
|
entity |
| Predicate | maximumTransferMode |
P31491
|
FINISHED |
| Object | Ultra DMA mode 4 |
—
|
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: Ultra DMA mode 4 | Statement: [ATA-5, maximumTransferMode, Ultra DMA mode 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTransferMode Context triple: [ATA-5, maximumTransferMode, Ultra DMA mode 4]
-
A.
maxDataTransferMode
chosen
Indicates the data transfer mode in which the maximum possible data throughput is achieved between entities.
-
B.
transferMode
Indicates the method or mechanism by which something is transferred from one entity to another.
-
C.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
D.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
E.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc610569d08190b108107dfe397f18 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.