Triple
T33029473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BITNET |
E845123
|
entity |
| Predicate | typicalLinkSpeed |
P139996
|
FINISHED |
| Object | 9600 bit/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: 9600 bit/s | Statement: [BITNET, typicalLinkSpeed, 9600 bit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLinkSpeed Context triple: [BITNET, typicalLinkSpeed, 9600 bit/s]
-
A.
passiveCableMaxSpeed
Indicates the maximum data transmission speed that can be supported when using a passive cable in the relationship.
-
B.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
C.
typicalMTU
Indicates that one entity is the typical or most common member type or unit associated with another entity.
-
D.
bandwidthCharacteristic
chosen
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
E.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:24 a.m.