Triple
T1774582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NuBus |
E38948
|
entity |
| Predicate | maximumTheoreticalBandwidth |
P1376
|
FINISHED |
| Object | about 40 MB/s at 20 MHz |
—
|
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: about 40 MB/s at 20 MHz | Statement: [NuBus, maximumTheoreticalBandwidth, about 40 MB/s at 20 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTheoreticalBandwidth Context triple: [NuBus, maximumTheoreticalBandwidth, about 40 MB/s at 20 MHz]
-
A.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
-
B.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
C.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
D.
memoryBandwidth
Indicates the rate at which data can be transferred to or from a memory system over a given period of time.
-
E.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.